Add Functionality to Ignore Nearly expired RIs with Specified Tags #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new feature to exclude expired Reserved Instances (RIs) when specific tags are associated with them, preventing them from being displayed as expired. The motivation behind this feature is to enhance the efficiency of frequent riex executions by excluding RIs that are nearing their expiration date but are already acknowledged.
To achieve this, the functionality leverages the capability of tagging EC2, Elasticache, and RDS instances with Reserved Instances. When a specified tag is present, the associated RIs are considered acknowledged and will be ignored, ensuring they are not included in the display results.
Please review and provide feedback on this pull request. Thank you!
Behavier
For example, RDS RI
in default:
if add --ignore-tags key1=value1;key2=value2
Currently, it is assumed that the recognized tags are attached manually.