-
Notifications
You must be signed in to change notification settings - Fork 340
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
ec2_vol - add support for modifying existing volumes #55
Comments
Files identified in the description: If these files are inaccurate, please update the |
Any update on this one or we just waiting 2.10 to be released? |
@roy-boy As it stands the ec2_vol module is a boto (v2) based module and I believe the original boto python module doesn't support changing the size of volumes. While it's possible to create a hybrid boto/boto3 module (as done in ansible/ansible#22978) this generally results in a much higher risk of bugs creeping into the module as boto and boto3 have very different approaches to parameters, return values and exceptions. There's a port of this module to boto3 in progress (#53). However, the bulk of contributors to both ansible.aws and community.aws are 'community' contributors and not directly paid to work on Ansible collections. As such, turn around can be much slower than people may like. Once #53 is merged reviving ansible/ansible#22978 should be relatively trivial. |
@tremble , thanks for your reply, yeah understand the release cycle of open source project. No worries I can use python boto3 now as the workaround for my project and keep an eye on the 2.10 release notes. Cheers! |
closed by #215 |
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
…ser. (ansible-collections#55) This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@4a0e1a4
SUMMARY
This is a re-submission of ansible/ansible#21588
A PR was opened to implement this but was ultimately closed without being merged seemingly due to disagreements over whether to require a complete port of the module to boto3:
ansible/ansible#22978
The need for the feature, particularly for expanding existing volumes, is still very real though.
ISSUE TYPE
COMPONENT NAME
ec2_vol
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: