-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Support tags for aws_db_snapshot data source #10010
Comments
Is anyone here? :) |
Especially when hex values are automatically added to db snapshot identifiers, as done in the TF RDS modules, the actual name of a snapshot is unknown so any data resource request fails. The tag filter extension is highly needed. |
bump |
Is there an update on this? I would love to have tags for the db snapshot identifier. |
This functionality has been released in v5.11.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. |
Community Note
Description
Currently, the aws_db_snapshot data source only supports finding snapshots by their id or their associated database id.
These options will not work for the use-case I have. Multiple DB snapshots are created outside of my terraform config, all with a standard naming convention and set of tags. I would like to reference the latest of those.
To do that, I would like to filter based on tags (similar to the usage in aws_ami). Alternatively, my problem could also be solved by allowing for wildcards in the snapshot identifier.
New or Affected Resource(s)
Potential Terraform Configuration
Here's an example of what this could look like in practice:
References
aws_db_instance
is Support tags for aws_db_instance data source #2988The text was updated successfully, but these errors were encountered: