-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
fix imagebuilder-pipeline image_recipe_arn ForceNew #17137
fix imagebuilder-pipeline image_recipe_arn ForceNew #17137
Conversation
Hi @Goryudyuma 👋 Thank you for submitting this. Unfortunately this change is not valid -- the terraform-provider-aws/aws/resource_aws_imagebuilder_image_pipeline.go Lines 254 to 303 in 9a94e4f
Which is verified with the terraform-provider-aws/aws/resource_aws_imagebuilder_image_pipeline_test.go Lines 238 to 270 in 9a94e4f
So while Terraform may not be operating as you expect in this situation, the resource and schema are currently valid. My best suggestion would be to potentially open a GitHub issue following the issue template so the maintainers can attempt to troubleshoot any potential bugs or if you have a question about how Terraform is operating to use the HashiCorp Community Forums where there are far more people ready to help, whereas the GitHub issues here are generally monitored only by the small set of code maintainers. Very briefly though, you may want to see if your configuration should be using the |
Hi @bflad ! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Relates OR Closes #0000
Release note for CHANGELOG:
Output from acceptance testing:
If you keep the previous settings, you will get an error when you change "image_recipe".
This is a phenomenon that occurs when "image_recipe" cannot be deleted because "ImagePipeline" depends on "image_recipe".
After making this change, the "ImagePipeline" will be recreated and no error will occur.
What I want is that changing "image_recipe" doesn't cause "ImagePipeline" to be an error.
This PR can do that, but if there's a better way, that's fine.
Please tell me what to do after this.