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
The ec2.py dynamic inventory script does not group RDS instances by tag #14464
Comments
As an ugly workaround, you can append the environment name to the RDS instance's For example:
|
#15609 does not solve this issue. It provides tags for RDS clusters, but not RDS instances. Why would clusters have received this fix before instances? What obstacles remain to expose the resource tags of RDS instances via dynamic inventory? |
@karlmdavis Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this issue with this template: |
Boto3 only at this time. Relates to ansible#11569, ansible#14464.
* Get tags for RDS instances. Boto3 only at this time. Relates to ansible#11569, ansible#14464. * Add a check for boto3 * Fix HAS_BOTO3 error
* Get tags for RDS instances. Boto3 only at this time. Relates to ansible#11569, ansible#14464. * Add a check for boto3 * Fix HAS_BOTO3 error
* Get tags for RDS instances. Boto3 only at this time. Relates to ansible#11569, ansible#14464. * Add a check for boto3 * Fix HAS_BOTO3 error
Any movement on this issue since May? Seems to not be supported still and would be useful for our use case. |
@karlmdavis You have not responded to information requests in this issue so we will assume it no longer affects you. If you are still interested in this, please create a new issue with the requested information. |
This makes it unpossible to delete (or otherwise poke at) RDS instances by tag. This would be useful in all the same ways that grouping EC2 instances by tag, e.g. for maintaining separate dev/production instances via an "Environment" tag.
The text was updated successfully, but these errors were encountered: