boundary_account_oidc resource throws error on second apply when subject is specified.

[AntPAllen]

Terraform Version

Terraform v1.0.0
on linux_amd64

• provider registry.terraform.io/hashicorp/boundary v1.0.2

Affected Resource(s)

boundary_account_oidc

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

resource "boundary_account_oidc" "oidc_account" {
  auth_method_id = boundary_auth_method_oidc.oidc.id
  subject = "xxxxx"
}

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Panic Output

Expected Behavior

Every apply should run without error

Actual Behavior

First apply works, but subsequent apply's throws error due to subject field not being updatable.

Steps to Reproduce

1. terraform apply
2. terraform apply

│ Error: error updating account: {"kind":"InvalidArgument","message":"Error in provided request.","details":{"request_fields":[{"name":"attributes.subject","description":"Field cannot be updated."}]}}

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• GH-1234

[malnick]

Thanks for opening this. We've triaged this as a question for now but are looking into the possibility that this is a bug in the way the provider is implemented. We'll update this issue soon, thanks!

[malnick]

PR to fix this bug: #122

[malnick]

@AntPAllen - can you build from the latest main commit and verify #122 fixes this for you?

Thank you!

[AntPAllen]

Sorry for the late reply, but I can confirm this resolves the issue. Thank you!