This repository was archived by the owner on Jun 4, 2021. It is now read-only.
ec2 to ec2_instances module migration #1706
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… zones and cheaper and more performance
… more boto3 based modules and newer ansible versions
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
in this pull, I'm laying the groundwork to support later Ansible version where the ec2 module will be deprecated in favor of ec2_instances
Currently, there are a few modules that only recently got merged in ansible 2.10 devel that will allow us to move the metric module to support boto3. This will allow us to enable the new zones like me-south-1 that are currently not supported with boto and they don't accept pull requests for it.