-
Notifications
You must be signed in to change notification settings - Fork 341
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
Migrate ec2 vpc endpoint modules #392
Conversation
* Rename core collection Rename references to ansible.amazon to amazon.aws. * Rename community.amazon to community.aws Fix pep8 line lengths for rewritten amazon.aws imports * Missed a path in shippable.sh * Dependency repos moved
* Remove ANSIBLE_METADATA entirely, see ansible/ansible/pull/69454. Remove `license` field from galaxy.yml, in favor of `license_file`.
* Update module deprecations Switch version to `removed_at_date` * Don't install amazon.aws from galaxy We've been using galaxy to install amazon.aws in shippable, but that doesn't really work if we aren't publising faster. Get that collection from git so it is most up to date. * We need to declare python test deps now * missed a python dep
Updated module examples with FQCN Signed-off-by: Abhijeet Kasurde <[email protected]>
* Update docs Remove .git from repo url so links in readme will generate correctly Add required ansible version Run latest version of add_docs.py Add version_added string to modules * galaxy.yml was missing authors
Signed-off-by: Abhijeet Kasurde <[email protected]>
* Update comments to reference AnsibleAWSModule rather than AnsibleModule * Bulk re-order imports and split onto one from import per-line. * Add AnsibleAWSModule imports * Migrate boto 2 based modules to AnsibleAWSModule * Move boto3-only modules over to AnsibleAWSModule * Remove extra ec2_argument_spec calls - not needed now we're using AnsibleAWSModule * Remove most HAS_BOTO3 code, it's handled by AnsibleAWSModule * Handle missing Boto 2 consistently (HAS_BOTO) * Remove AnsibleModule imports * Changelog fragment
…r(e) or e.me… (ansible-collections#26) * Py3 compat error handling: use to_native(e) instead of str(e) or e.message * PR comment changes, use fail_json_aws and is_boto3_error_code
…ollections#188) * Migrate from boto3_conn to module.client * Simplify error handling when creating connections * Simplify Region handling * Remove unused imports * Changelog
* Split imports and reorder * Import camel_dict_to_snake_dict and snake_dict_to_camel_dict direct from ansible.module_utils.common.dict_transformations * Remove unused imports * Route53 Info was migrated to Boto3 drop the HAS_BOTO check and import * changelog
* Split imports and sort * Move camel_dict_to_snake_dict imports to ansible.module_utils.common.dict_transformations * Cleanup unused imports * Bulk migration to fail_json_aws * Changelog
* deprecate policy_file * ignore file * changelog
* Ensure ec2_vpc_endpoint returns True when deleting an Endpoint Return not changed when state=absent and endpoint has already been deleted * Add minimal endpoint tests
* More aliases cleanup * Mark ec2_classic_lb tests unstable * Add more comments about why tests aren't enabled
* Added support for 'vpc_endpoint_type'. * Integration test for the 'vpc_endpoint_type' feature. * Added choices in documentation. * Added changelog.
* Add no_log=False to mark some more false-positives of the no_log check. * More false-positives confirmed by tremble.
* New module - ec2_vpc_endpoint_service_info * Deprecate querying services through ec2_vpc_endpoint_info * Attempt to cope with some services which have who possible endpoints Co-authored-by: Jill R <[email protected]>
* Stabilize and improve ec2_vpc_endpoint modules - Add tagging support - Make idempotent - Better exception handling - Better check_mode support - Use module_utils for common functions - Enable retries on common AWS failures * Make endpoint deletion idempotent in check_mode * Sanity fixes * Address review feedback
recheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with #298 boto3 became the default requirement for modules, this isn't the case for community.aws yet
version_added: 1.5.0 | ||
description: | ||
- Gets details related to AWS VPC Endpoint Services. | ||
requirements: [ boto3 ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
requirements: [ boto3 ] |
post #298 this isn't needed in amazon.aws (ansible-collections/community.aws#569 is still pending)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shoot, 569 is totally on me - thanks! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
569 has now been merged, not sure how you'd like to handle the updates here.
description: | ||
- Gets various details related to AWS VPC endpoints. | ||
- This module was called C(ec2_vpc_endpoint_facts) before Ansible 2.9. The usage did not change. | ||
requirements: [ boto3 ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
requirements: [ boto3 ] |
- Creates AWS VPC endpoints. | ||
- Deletes AWS VPC endpoints. | ||
- This module supports check mode. | ||
requirements: [ boto3 ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
requirements: [ boto3 ] |
Disable the `squash-merge` merge strategy just the time we land ansible-collections/amazon.aws#392
I add a Depends-On: ansible/project-config#862 to be sure we don't squash the commits during the PR landing :-). |
@jillr, I've pushed https://github.com/ansible-collections/amazon.aws/pull/393/commits which is based on your branch. The difference is that I add a footer in the commit message. It includes a URL pointing on the original commit. I use the following script to build this up: https://github.com/goneri/promote_aws_modules |
@goneri Should we close this and do all of the migrations with the automation? Or do you think it's worth landing this one since the PR is open? |
@jillr, we can actually close both and reopen a clean PR. I did the script as a proof of concept but anyone can actually continue from that. |
We have a new way of doing these; closing and will open a new PR |
* Remove cloudformation (amazon.aws) placebo recordings * Move module unit tests to the right location so ansible-test finds them
* Remove cloudformation (amazon.aws) placebo recordings * Move module unit tests to the right location so ansible-test finds them This commit was initially merged in https://github.com/ansible-collections/community.aws See: ansible-collections/community.aws@1cf83b1
Depends-On: ansible/project-config#862
SUMMARY
Moves ec2_vpc_endpoint, ec2_vpc_endpoint_info, and ec2_vpc_endpoint_service_info from community.aws to amazon.aws via git patch.
As discussed at #354 (review), this PR initially demonstrates the result of the git patch process. When that is approved, the git patch process will be repeated directly onto
main
to preserve git history. This PR will then be rebased on the updatedmain
with the runtime.yml, deprecation, and example documentation changes.ISSUE TYPE
COMPONENT NAME
ec2_vpc_endpoint
ec2_vpc_endpoint_info
ec2_vpc_endpoint_service_info
ADDITIONAL INFORMATION
Patch process: