v1.19.0

chore: Link for ArgoCD Bot User @milldr (#729)

what

• Corrected link for ArgoCD bot user

why

• This paragraph's intention is to direct to an FAQ for using the bot user to create ArgoCD repos rather than manually creating the repos (optional)

references

• https://github.com/orgs/cloudposse/discussions/42
• DEV-3060

♻️ chore: Quickstart Improvements @cloudpossebot (#727)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#734

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#734

v1.18.0

Announce Quickstart Sponsorship @osterman (#728)

what

• Change the announcement CTA to promote quickstart sponsorship
• Disable formatOnSave for .mdx files as it messes up the formatting of lists
• Fix formatting of lists

why

• Make it more obvious that the configurations are only available via GitHub Sponsors

highlights

v1.17.0

chore: Replaced All Atlassian Links @milldr (#726)

what

• Replaced or deleted every atlassian link

why

• We dont use confluence anymore. Each out dated reference needs to be updated or delete

references

• Email, customer was redirected to atlassian

v1.16.0

Fix: Edit Link @milldr (#725)

what

• Fix the default link for editing files

why

• The link for any page to edit should work!

references

• n/a

♻️ fix: corrections to gitops apply and add tofu @cloudpossebot (#724)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#729

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#729

v1.15.0

DEV-2617: Improved AtmosWorkflows @milldr (#703)

what

• Handle recursive AtmosWorkflow calls
• Handle "echo" titles
• Better format shell scripts inside workflows

why

• Improved user experience. No commands are hidden behind workflows

references

• DEV-2617
• DEV-2494

examples

Workflow with nothing special

1. Each workflow step is a separate docs "Step"
2. Add the workflow description

Example: https://pr-703.cloudposse-docs.ue2.dev.plat.cloudposse.org/layers/eks/deploy-clusters/#-deploy-platform-dev-cluster-resources

Workflow with command grouping

1. Using the echo command step to designate the group start
2. Put all steps in the group into 1 code block

Example: https://pr-703.cloudposse-docs.ue2.dev.plat.cloudposse.org/layers/network/dns-setup/#-deploy-dns-components

Workflow with vendoring

1. Combine all vendor steps into 1 code block

Example: https://pr-703.cloudposse-docs.ue2.dev.plat.cloudposse.org/layers/eks/deploy-clusters/#-vendor-components

fix: renovate config link is broken @Gowiem (#721)

what

• Cloud Posse needs a new link for the renovate config file that they shared in this doc.

why

• Link is broken -- It goes no where.

references

• https://docs.cloudposse.com/learn/maintenance/upgrades/how-to-keep-everything-up-to-date/
• Also, FYI folks: Your "Edit this page" link at the bottom of the docs site is broken as well. It's introducing an extra /content/ into the URL. I didn't go digging for where this happening within your docs site generation.

Fix admonition regarding component migration @osterman (#720)

what

• Clarify that the GitHub repository has moved, not the documentation

why

• Previously we made it look like the documentation has migrated

v1.14.0

DEV-2741: Cold Start Improvements and EKS FAQs @milldr (#717)

what

• Added 2 FAQs for EKS
• QoL improvements to cold start

why

• I encountered both of these issues when deploying EKS and the cold start recently

references

• DEV-2741
• DEV-2651
• https://github.com/orgs/cloudposse/discussions/26

v1.13.0

Components migration docs @goruha (#716)

what

• Components migration docs

why

• Document or Script Process for Customers so they can update component.yaml

references

• cloudposse/terraform-aws-components#1177

v1.12.0

Update terraform/opentofu design decision @osterman (#715)

what

• Update design decision on using OpenTofu vs BSL Terraform.
• Add design-decision tag to all decisions
• Add admonition concerning design decisions to quickstart and jumpstart packages

why

• Provide the context surrounding the BSL license change so everyone is informed
• Ensure there's less confusion around what's offered in the jumpstart and quickstart packages

New org components @goruha (#713)

what

• Generate components docs from cloudposse-terraform-components org
• Update PyGithub pip package
• Added docs/components/library/aws/spacelift/README.md and docs/components/library/aws/tgw/README.md
• Fix links referenced to renamed components

1. /components/library/aws/aws-sso -> /components/library/aws/identity-center
2. /components/library/aws/eks/karpenter/ -> /components/library/aws/eks/karpenter-controller/
3. components/library/aws/datadog-configuration -> components/library/aws/datadog-credentials
4. /components/library/aws/argocd-repo/ -> /components/library/aws/argocd-github-repo/

• Added redirect rule for renamed components
• Refactor docs-collator for components
• Added docs grouping (ex.: glue, spacelift, tgw)
• Added components preserve provider in name on docs site (ex.: aws-config)

why

• Migrate components to new organization
• Version 2 support rate-limiting so script would not fail because hitting the rate
• This is the only place where it makes sense to put that docs because spacelift and tgw components now in new repos
• Avoid build failing because of broken links
• Preserve links indexed by search engine working
• Improve code quality
• As we have each component in a separate repo, we need a way how to group them at the docs site
• Some components need to preserve aws- in the interest of readability

v1.11.0

Fix build website action @goruha (#714)

what

• Provide GitHub token to render-docs-for-components.sh

why

• MIgrate components to new cloudposse-terraform-components org

feat: Decide on Default Storage Class for EKS Clusters @milldr (#711)

what

• Add decision guide for default storage class in EKS clusters

why

• ADR for EFS vs EBS

references

• n/a

♻️ Benbentwo/customer generation @cloudpossebot (#712)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#716

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#716

♻️ WIP - feat: EKS Implementation Upstreams @cloudpossebot (#707)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#713

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#713

v1.10.0

feat: FAQ for `dns-delegated` `gbl` deployment @milldr (#710)

what

• FAQ for "Why should the dns-delegated component be deployed globally rather than regionally?"

why

• common question in slack

references

• slack

♻️ fix: Makefile Snippet @cloudpossebot (#709)

[!IMPORTANT]
Do not merge this PR manually. It will be handled automatically by the cloudposse/refarch-scaffold repository.
Instead, please review the changes and merge cloudposse/refarch-scaffold#715

What

This pull request was created by the 🚀 Generate Examples workflow in the cloudposse/refarch-scaffold repository. This PR updates this documentation repo with the latest configuration for the Cloud Posse reference architecture.

Why

This documentation repo is used for reference purposes and should have the latest configuration.

References

Internal PR: cloudposse/refarch-scaffold#715