📢 Migration of Components to a New GitHub Organization complete!

[osterman]

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-components repository 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:

• Leverage terratest automation for better testing.
• Implement semantic versioning to clearly communicate updates and breaking changes.
• Improve PR review times and accelerate community contributions.
• Enable Dependabot automation for dependency management.
• And much more!

What to Expect Starting November 12, 2024

• Migration Timeline: The migration will begin on November 12 and is anticipated to finish by the end of the following week.
• Code Freeze: Starting on November 12, this repository will be set to read-only mode, marking the beginning of a code freeze. No new pull requests or issues will be accepted here after that date.
• New Contribution Workflow: After the migration, all contributions should be directed to the new individual component repositories.
• Updated Documentation: To support this transition, we are updating our documentation and cloudposse-component updater.
• Future Archiving: In approximately six months, we plan to archive this repository and transfer it to the cloudposse-archives organization.

Frequently Asked Questions

• Does this affect Terraform modules? No, only the terraform-aws-components repository 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

[mtb-xt]

Will there be any guidance on how to update our reference architectures to use this new setup?

[goruha]

@mtb-xt for sure
We prepared PR to component-updater GHA that will migrate components to the new org smoothly.
But we will also create documentation on how you can migrate manually.

[osterman]

@mtb-xt just to clarify what @goruha said, we've updated the component-updater GitHub Action to automatically rewrite the sources in the vendor and component manifest files when it opens the PRs. This should make the upgrade transparent and painless.

[nitrocode]

Very cool. Looking forward to seeing all the components tested.

1. Will all the same components be available after the migration?

2. Will components still be open source?

3. What will the new organization be named?

   Looked through the source code of the component updater and saw this https://github.com/cloudposse-terraform-components

4. Will the component updater be updated to allow overriding the above org to use different sources if needed?

5. Would you folks consider opening up the codeowners for components once they are all in their own repositories like you folks do with terraform modules ?

Thanks!