📢 Migration of Components to a New GitHub Organization complete! #1177
Comments
osterman
changed the title
|
Will there be any guidance on how to update our reference architectures to use this new setup? |
|
@mtb-xt just to clarify what @goruha said, we've updated the |
goruha
changed the title
|
Very cool. Looking forward to seeing all the components tested.
Thanks! |
|
@nitrocode thanks for raising these questions.
Yes, we have no plans to change license.
Correct, you found it! https://github.com/cloudposse-terraform-components As part of our transition to GitHub Enterprise (GHE), we are reorganizing our open-source projects into more purpose-built organizations. This allows us to better manage repository rulesets, GitHub Apps, and other configurations specific to each organization's purpose. This approach enhances our security posture and improves discoverability. Additionally, keeping our components separate from less opinionated child modules avoids confusion and ensures clearer organization.
The component updater uses the sources as define in the vendor and component manifests. Thus, that's supported today. One thing we've added to the component updater to make this switch less painful, is the ability for it to rewrite the sources to their new homes. So if it see's references to components in
Yes, so we'll be able to accept more contributions of components and delegate ownership of components with this move. Note, |
goruha
changed the title
|
@osterman @goruha One thing I noticed is that the git history for each component was lost. It's probably too late now to see if that can be retained, but I wanted to point it out in case others were looking for older history, then it would be good to archive terraform-aws-components repo for posterity. Edit: oh right just reviewed the post again and saw this
|
|
@nitrocode I re-run the migration script and copied the git history. You can check this repo as an example https://github.com/cloudposse-terraform-components/aws-bastion/commits/main/ |
## what * Automatically migrate existing components to the new GitHub organization ## why * Makes migration to new component structure simple and stable ## Refs * cloudposse/terraform-aws-components#1177
|
Awesome, I see the history now. Thank you! |
|
Last nitpick, I see the references in the readme for each component often link back to this repo which is soon to be archived. E.g. https://github.com/cloudposse-terraform-components/aws-iam-role?tab=readme-ov-file#references |
Hello, Cloud Posse Community!
We’re excited to announce that starting on November 12, 2024, we will begin migrating each component in the
cloudposse/terraform-aws-componentsrepository to individual repositories under a new GitHub organization. This change aims to improve the stability, maintainability, and usability of our components.Why This Migration?
Our goal is to make each component easier to use, contribute to, and maintain. This migration will allow us to:
terratestautomation for better testing.What to Expect Starting November 12, 2024
cloudposse-componentupdater.cloudposse-archivesorganization.Frequently Asked Questions
terraform-aws-componentsrepository is affected. Our Terraform modules will remain where they are.We are committed to making this transition as seamless as possible. If you have any questions or concerns, please feel free to post them in this issue. Your feedback is important to us, and we appreciate your support as we embark on this new chapter!
Thank you,
The Cloud Posse Team
The text was updated successfully, but these errors were encountered: