From 007dc2e259b072119fc7b2adbe4015c497d07b6f Mon Sep 17 00:00:00 2001 From: Igor Rodionov Date: Fri, 22 Nov 2024 19:33:42 +0100 Subject: [PATCH] Components migration docs --- .../how-to-update-components-yaml-to-new-organization.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization.mdx b/docs/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization.mdx index 725bb56f6..ac7ace598 100644 --- a/docs/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization.mdx +++ b/docs/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization.mdx @@ -10,7 +10,7 @@ import KeyPoints from '@site/src/components/KeyPoints'; ## Problem Cloud Posse migrated each component in the `cloudposse/terraform-aws-components` repository to individual repositories -under a new [`cloudposse-terraform-components` GitHub organization](https://github.com/orgs/cloudposse-terraform-components). +under a new [`cloudposse-terraform-components`](https://github.com/orgs/cloudposse-terraform-components) GitHub organization. This change aims to improve the stability, maintainability, and usability of our components. Now all components are available in the new organization, and we need to update the references in the `component.yaml` files