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

Fix admonition regarding component migration #720

Merged
merged 1 commit into from
Dec 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 9 additions & 13 deletions docs/components/components.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,19 @@ sidebar_position: 0
sidebar_class_name: hidden
description: Library of Terraform Root Module Components
---
import Intro from '@site/src/components/Intro';
import DocCardList from '@theme/DocCardList';

<Intro>
This is a library of reusable Terraform "root module" components.
</Intro>
import Intro from "@site/src/components/Intro";
import DocCardList from "@theme/DocCardList";

<DocCardList/>
<Intro>This is a library of reusable Terraform "root module" components.</Intro>

:::info
## The Components In This Repository Have Moved!

We've migrated all the components to individual repositories under a [dedicated GitHub organization](https://github.com/cloudposse-terraform-components).
All future updates, contributions, and issues should be directed to the respective component repositories in the new organization.
<DocCardList />

[Learn more](/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization/) how to migrate your components references to new repos.
:::
:::info

## Terraform Component GitHub Repository Has Moved!

The GitHub repository for Cloud Posse's Terraform components has migrated to a [dedicated GitHub organization](https://github.com/cloudposse-terraform-components). All documentation remains here, but all future updates, contributions, and issue tracking for the source code should now be directed to the respective repositories in the new organization.

[Learn more](/learn/maintenance/tutorials/how-to-update-components-yaml-to-new-organization/) about updating your references to point to the new repositories.
:::
Loading