-
Notifications
You must be signed in to change notification settings - Fork 9k
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 in aws_service_discovery_private_dns_namespace #7840
Comments
aws_service_discovery_private_dns_namespace
Hi @barnharts4 👋 It does not appear that Cloud Map currently supports this functionality in its API, which means support within the Terraform AWS Provider is not likely to be implemented at the current time due to its potential maintenance burden. I would suggest reaching out to AWS through your Support or TAM channels to request this functionality and we will be happy to include it if/when its natively supported by the API. |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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
aws_service_discovery_private_dns_namespace
does not support adding tags. However, it creates a Route53 hosted zone, which costs money monthly. Since we use tags to track and allocate costs, we have no way to have this resource's hosted zone reflected in our cost reporting by tag.Please add support for adding a
tags
collection to this resource which will propagate to all underlying AWS resources that support tags.New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: