-
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
[Bug]: New revisions of aws_batch_job_definition forgets tags #39795
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.73.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! |
Terraform Core Version
1.8.3
AWS Provider Version
5.72.1
Affected Resource(s)
Expected Behavior
When making changes to an aws_batch_job_definition with tags, newly introduced revisions of the job definition should continue to be tagged with the tags specified in the Terraform file.
Actual Behavior
When making changes to an aws_batch_job_definition with tags, newly introduced revisions are not tagged. Only the first revision carries the tags specified in the Terraform file.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Observe that revision 2 is not tagged:
Expected revision 2 to be tagged.
Debug Output
N/A
Panic Output
N/A
Important Factoids
N/A
References
N/A
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: