IBM Cloud Terraform provider v2.5.0: ibm_iam_user_invite fails with "already ACTIVE" for existing members

TL;DR

What was going on After upgrading the IBM Cloud Terraform provider to v2.5.0, ibmiamuser_invite was no longer idempotent: if a user was already an active member of the account, terraform apply failed with: [ERROR] User invite unsuccessful: user(s) [...] are already ACTIVE in account..., which means they were already invited and onboarded to the account earlier.

Steps

1. What was going on

After upgrading the IBM Cloud Terraform provider to v2.5.0, ibmiamuser_invite was no longer idempotent: if a user was already an active member of the account, terraform apply failed with: [ERROR] User invite unsuccessful: user(s) [...] are already ACTIVE in account ..., which means they were already invited and onboarded to the account earlier. Previously the invite was a no-op. The regression came in via PR #6902, and import is not supported for this resource, so there was no way to absorb externally-added users into state.

2. What fixed it

This was a provider regression in v2.5.0 , upgrade to v2.6.0 or later, where the reporter confirmed it is fixed (the maintainer's fix PR restored the idempotent behavior). If you are stuck on v2.5.0, the workaround is to remove already-onboarded users from the users list before applying. Source: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6953

When to use

You are seeing this: Previously the invite was a no-op. Use this skill when you run into "IBM Cloud Terraform provider v2.5.0: ibmiamuser_invite fails with "already ACTIVE" for existing members".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v2.5.0, v2.6.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6953

In the thread, the question was: After upgrading the IBM Cloud Terraform provider to v2.5.0, ibmiamuserinvite was no longer idempotent: if a user was already an active member of the account, terraform apply failed with: [ERROR] User invite unsuccessful: user(s) [...] are already ACTIVE in account ..., which means they were already invited and onboarded to the account earlier. Previously the invite was a no-op. The regression came in via PR #6902, and import is not supported for this resource, so there was no way to absorb externally-added users into state. The verified resolution: This was a provider regression in v2.5.0 , upgrade to v2.6.0 or later, where the reporter confirmed it is fixed (the maintainer's fix PR restored the idempotent behavior). If you are stuck on v2.5.0, the workaround is to remove already-onboarded users from the users list before applying. Source: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6953 Thread: https://vectle.com/threads/thrWQFyZhGRIY_flmG4Wu4GTg