Skip to content
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

Rename collection #13

Merged
merged 5 commits into from
Mar 25, 2020
Merged

Rename collection #13

merged 5 commits into from
Mar 25, 2020

Conversation

jillr
Copy link
Collaborator

@jillr jillr commented Mar 23, 2020

SUMMARY

Content collections may not be published to the ansible namespace. As such,
rename collection, imports, and other relevant paths to amazon.aws.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

amazon.aws

ADDITIONAL INFORMATION

Additional PRs will follow (in multiple repos) to:

  1. Update relevant references in community.amazon to use the new FQCN for this collection
  2. Rename community.amazon to community.aws
  3. Point references to community.amazon in this repo (integration tests) to the renamed community.aws
  4. Update https://github.com/ansible/ansible/blob/devel/lib/ansible/config/routing.yml to the new collection names

Content collections may not be published to the ansible namespace. As such,
rename collection, imports, and other relevant paths to amazon.aws.
@jillr
Copy link
Collaborator Author

jillr commented Mar 25, 2020

I've hacked things up a bit so that community.amazon has the new import paths (so for example the tests that call ec2_instance can pass) by having shippable.sh use the branch from this PR: ansible-collections/community.aws#12
That PR will be updated to also rename community.amazon to community.aws as noted in bullet point 2 outlined in this PR. Then when that lands, I'll revert shippable.sh in this collection to use master from community.aws.

@jillr jillr merged commit fba5580 into ansible-collections:master Mar 25, 2020
@jillr jillr deleted the fqcn_change branch February 24, 2021 17:25
jillr pushed a commit to jillr/amazon.aws that referenced this pull request May 3, 2021
Coverage versions 5 and later are not supported by ansible-test.
jillr pushed a commit to jillr/amazon.aws that referenced this pull request May 10, 2021
Coverage versions 5 and later are not supported by ansible-test.
jillr pushed a commit to jillr/amazon.aws that referenced this pull request May 10, 2021
Coverage versions 5 and later are not supported by ansible-test.
jillr pushed a commit to jillr/amazon.aws that referenced this pull request May 13, 2021
Coverage versions 5 and later are not supported by ansible-test.
goneri pushed a commit that referenced this pull request Sep 20, 2022
Coverage versions 5 and later are not supported by ansible-test.

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections/community.aws@c2bb050
GomathiselviS pushed a commit to GomathiselviS/amazon.aws that referenced this pull request Sep 20, 2022
Coverage versions 5 and later are not supported by ansible-test.

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections/community.aws@c2bb050
abikouo pushed a commit to abikouo/amazon.aws that referenced this pull request Oct 24, 2023
Coverage versions 5 and later are not supported by ansible-test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant