-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
batch/job_definition: Fix for ARN updating #37111
Conversation
Community NoteVoting for Prioritization
For Submitters
|
Thank you for your contribution! 🚀 A new usage of AWS SDK for Go V1 was detected. Please prefer AWS SDK for Go V2 for all net-new services. If this is an enhancement or bug fix to an existing AWS SDK Go V1 based resource, this comment can be safely ignored. For additional information refer to the AWS SDK for Go Versions page in the contributor guide. |
This functionality has been released in v5.47.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Recent changes in hashicorp/terraform-provider-aws#37111 introduced a Diff customizer that leads to errors in the Pulumi version of the provider due to discrepancies in the order in which Diff customizer functions are applied between Pulumi and Terraform. This change fixes the problem by applying the experimental PlanResourceChange flag to the affected resource. A regression test is included. See also: pulumi/pulumi-terraform-bridge#1785
…3888) Recent changes in hashicorp/terraform-provider-aws#37111 introduced a Diff customizer that leads to errors in the Pulumi version of the provider due to discrepancies in the order in which Diff customizer functions are applied between Pulumi and Terraform. This change fixes the problem by applying the experimental PlanResourceChange flag to the affected resource. Fixes #3887 A regression test is included. See also: pulumi/pulumi-terraform-bridge#1785
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
There is a challenge determining if the Job Definition needs to be updated. This is the cost of not forcing new when updates to one argument (eg,
container_properties
) simultaneously impact a computed attribute (eg, arn). This is a similar situation faced with Lambda Function but Job Definition seems more difficult in determining when a change will cause a revision. The real tricky challenge here is that we have to figure out if a change is GOING to cause a new revision to be created, without the benefit of AWS just telling us. This is necessary because waiting until after AWS tells us is too late, and practitioners will need to refresh or worse, get an inconsistent plan. BUT, if weSetNewComputed
without a change, we'll get a testing error:"the non-refresh plan was not empty"
.Relations
Closes #36894
Closes #36824
Closes #36865
Relates #35149
References
Output from Acceptance Testing