Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #11258 #12595

Merged

Conversation

de-husk
Copy link
Contributor

@de-husk de-husk commented Mar 10, 2017

Bug: #11258
If the user_arn changes on the opsworks user profile resource we should delete it and recreate it instead of attempting to modify it incorrectly and causing the terraform apply to fail.

I also added an acceptance test that will trigger this case.

If the user_arn changes on the user_profile resource we should delete it and recreate it
instead of attempting to modify it incorrectly and causing the terraform apply to fail.

I also added an acceptance test that will trigger this case.
@radeksimko
Copy link
Member

Thanks for the PR, I was able to reproduce the issue. Even though it's not entirely clear from the docs I understand the IAM User ARN is used as a unique identifier for the user profile and there's always 1-1 mapping between IAM user and the opsworks profile.

Also thanks for the test! 👍

TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSOpsworksUser -timeout 120m
=== RUN   TestAccAWSOpsworksUserProfile
--- PASS: TestAccAWSOpsworksUserProfile (29.85s)
PASS
ok  	github.com/hashicorp/terraform/builtin/providers/aws	29.880s

@radeksimko radeksimko merged commit f28c811 into hashicorp:master Mar 13, 2017
radeksimko pushed a commit that referenced this pull request Mar 13, 2017
If the user_arn changes on the user_profile resource we should delete it and recreate it
instead of attempting to modify it incorrectly and causing the terraform apply to fail.

I also added an acceptance test that will trigger this case.
yanndegat pushed a commit to yanndegat/terraform that referenced this pull request Mar 13, 2017
If the user_arn changes on the user_profile resource we should delete it and recreate it
instead of attempting to modify it incorrectly and causing the terraform apply to fail.

I also added an acceptance test that will trigger this case.
@ghost
Copy link

ghost commented Apr 15, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants