v1.28.0

chore: Improve SuperAdmin docs @milldr (#747)

what

• improved SuperAdmin docs

why

• This page was missing our standard conventions for documentation

references

• DEV-3154

chore: Deprecated `#refarch` References @milldr (#749)

what

• removed all occurrences of #refarch

why

• We have archived that channel and now require all support questions in GitHub Discussions

references

• https://github.com/orgs/cloudposse/discussions

v1.27.0

Improve Deployment Ordering Documentation @milldr (#746)

what

• Move ECR to after GitHub
• Add planners and necessary steps to reapply aws-teams

why

• Improve the documentation ordering for deploying github oidc related components

references

• https://github.com/orgs/cloudposse/discussions/57
• requires #745
• requires cloudposse/refarch-scaffold#749

♻️ Improve Deployment Ordering @milldr (#745)

[!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#749

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#749

v1.26.0

Update docs for Geodesic v4 @Nuru (#722)

what

• Update Geodesic documentation for version 4

why

• Existing documentation is out of date and does not reflect current best practices

references

• https://github.com/cloudposse/geodesic/blob/main/ReleaseNotes-v4.md

DEV-2495: Update FAQ for GitOps Labels @milldr (#744)

what

• Add a FAQ for all GitOps labels

why

• the previous list was incomplete

references

• DEV-2495

DEV-2502: Reference Page Introduction @milldr (#743)

what

• Add introductory content to the reference section

why

• Replace the placeholder. Explain this page

references

• DEV-2502

DEV-2490: Formatting for Compliance Setup @milldr (#742)

what

• Fix the formatting for compliance and security set up

why

• Steps were not formatting correctly

references

• DEV-2490

v1.25.0

chore: Community Testing Documentation Improvements @milldr (#741)

what

• Clean up the documentation pages for testing

why

• Update conventions, formatting, spelling
• Add FAQs I've encountered

references

• n/a

feat: Poly Repo Strategy @milldr (#740)

what

• Document poly repo strategy with account-map

why

• This has come up a few times recently

references

• https://github.com/orgs/cloudposse/discussions/49

Argo CD GitHub App Usage @milldr (#739)

what

• Document using GitHub Apps for Argo CD rather than GitHub PATs

why

• GitHub Apps are now supported for Argo CD as the preferred auth method.

references

• .

DEV-123: Update Release Engineering docs to include snippet on consolidating workflows @Benbentwo (#708)

what

• Update Release Engineering docs to include snippet on consolidating workflows

why

• Docs
• More upfront docs during handoff

v1.24.0

Fix component testing cheatsheet @goruha (#738)

what

• Fix component testing cheatsheet

why

• Current cheatsheet have wrong info

v1.23.0

feat: Announcements @milldr (#737)

what

• Create support for Announcements

why

• We need somewhere to put announcements that we can link and refer to

references

• Slack

v1.22.0

Address @osterman comments @goruha (#736)

what

• Address @osterman comments from #733 (review)

why

• Improve documentation

references

• #733 (review)

v1.21.0

Component testing guide @goruha (#733)

what

• Added writing components testing guide

why

• Allow contributors to add components tests

v1.20.1

Improve the Onboarding Workflow @osterman (#735)

what

• Change banner wording to "Start here!"
• Introduce what the documentation is for and why we sell it

why

• Make it more clear that to follow the documentation, they need the configuration

v1.20.0

Introduce Cloud Posse Support Options @osterman (#734)

What

• Introduce Essential, Flexible, and Priority Support options
• Deprecate bundled support options previously included with Quickstart and Jumpstart
• Added tailwind support to simplify future CSS
• Created an expandable ActionCard that let's the CTA expand a list of options.

Why

• Bundled support was a "one size fits all" approach that didn't accommodate all needs
• New options allow customers to tailor their support package to fit their requirements
• Customers can adjust their support level based on budget and evolving needs

fix: Corrected Dockerfile path @milldr (#732)

what

• Set the path for the example snippet for the generated Dockerfile

why

• We have moved the default location for the Dockerfile

references

• cloudposse/refarch-scaffold#740

♻️ fix: Dockerfile Path for Docs @cloudpossebot (#731)

[!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#740

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#740

♻️ chore: Update geodesic version to 4.3.0 in baseline.yaml and Dockerfile @cloudpossebot (#730)

[!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#737

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#737