-
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
[Proposal] Default Tags Updates #29747
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.0.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! |
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. |
Description
Default Tags allow practitioners to define
tags
on the Provider and have them applied to resources, in addition to anytags
that are added to the resource itself. During the initial implementation there were known limitations that influenced howdefault_tags
could function and be applied. Since the initial implementation there have been updates to Terraform Plugin SDKv2 and the introduction of Terraform Plugin Framework. These updates will allow changes todefault_tags
that will address some of the limitations:With this update Default Tags would be able to:
Computed
values as a tagtags
on a resource match thedefault_tags
There will be no changes to how
default_tags
are configured within Terraform. Additionally, the goal is to implement this functionality on all resource that currently support tags, allowing for consistent behavior with all existing configurations.References
Issues
Go Docs
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: