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

v1.9.0

♻️ feat: Publish Makefile @cloudpossebot (#706)

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

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

feat: Dockerfile and Makefile Snippets @milldr (#705)

what

• Added Dockerfile for toolbox example

why

• Provide an example in docs

references

• DEV-2626

feat: Decide on Secrets Placement for Terraform @milldr (#702)

what

• Added design decision for placing Secrets in the account architecture

why

• We have a choice of where to store secrets that are used by Terraform

references

• customer

v1.8.0

♻️ Drift remediation fix aws cli @cloudpossebot (#690)

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

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

Fix: Miscellaneous Typos @milldr (#701)

what

• Fix typos across documentation

why

• Spelling and clean up

references

• n/a

♻️ Publish Dockerfile Example @cloudpossebot (#704)

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

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

v1.7.0

Fix: 1Pass SCIM Bridge Instructions @milldr (#700)

what

• Update SCIM bridge credentials and integration steps

why

• We should use the scimsession, not the bearer-token. Then enter the Bearer Token when prompted by the service

references

• Corrects #664

DEV-2606: Okta setup instructions @milldr (#699)

what

• Improve Okta SAML setup docs

why

• One step does not appear anywhere in Okta documentation. I was burnt by this and am adding docs to help future deployments

references

• DEV-2606

feat: ECS 1Password SCIM Bridge Guide @milldr (#664)

what

• Add guide for deploying ECS 1password SCIM bridge

why

• Helpful documentation

references

• engagement

feat(DEV-2537): Redirects @milldr (#685)

[!TIP]
use make start-production to enable redirects on local builds

what

• Set up redirects for legacy pages

why

• Route users to the appropriate page when using old links
• Support all REFARCH-xyz links

references

• DEV-2537

Self-Hosted Runners, EKS, and Leapp Design Decisions @milldr (#684)

what

• Added design decisions for self-hosted runner architecture and placement
• Added design decision for secrets management with EKS
• Added design decision for Leapp or alternatives

why

• These are decisions we make for all engagements and should be documented

references

• customer engagement
• https://github.com/cloudposse/terraform-aws-components/tree/main/modules/eks/github-actions-runner

v1.6.0

♻️ chore(deps): update cloudposse-github-actions/get-pr action to v2 @cloudpossebot (#689)

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

Use Collapsible Text instead of Details @milldr (#686)

what

• Replaced details with CollapsibleText for all Software Delivery pages

why

• More obvious to readers to understand that you should click these examples

references

• Internal slack
• https://linear.app/cloudposse/issue/DEV-2561/use-tabs-or-the-component-for-expandable-text-to-document-ecs

♻️ fix(DEV-2593): Atmos Stack Validation Errors @cloudpossebot (#688)

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

♻️ feat: add memorydb to addons @cloudpossebot (#683)

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

v1.5.0

feat: ECS Partial Task Definitions & GitHub OIDC setup @milldr (#687)

what

• Moved https://github.com/cloudposse/terraform-aws-components/blob/main/modules/ecs-service/docs/ecs-partial-task-definitions.md here
• Improve GitHub OIDC setup

why

• Advanced documentation should be included with these docs, since it's all public now. Originally this page was in componetns because we wanted it to be public, but now every thing is public anyway

references

• Slack

TODO

• After merging this PR, remove the duplicated docs page from terraform-aws-components

♻️ DEV-2539: Refactor Github Runner Workflows @cloudpossebot (#676)

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

fix: Philips Labs Steps Formatting @milldr (#675)

what

• Corrected Philips Labs steps format

why

• This step is sub topic of the previous step

references

• Internal slack
• Depends on cloudposse/refarch-scaffold#702

fix: Correct Karpenter Node Pool Docs @milldr (#674)

what

• added missed changes for karpenter node pool

why

• These are created in refarch-scaffold after we started the docs refactor

references

• https://github.com/cloudposse/refarch-scaffold/pull/681/files

v1.4.0

fix: Improved Links for Developer Onboarding @milldr (#671)

what

• Replace invalid link for Developer Onboarding
• Replace several "legacy" links to latest location for the same content

why

• The "Introduction to Toolset" slides have been replaced with a video
• Avoid using "legacy" links

references

• customer request

feat(DEV-2500): Identity Docs Improvements @milldr (#670)

what

• Improve identity documentation

why

• Incorporate identity feedback from previous PR

references

• #665
• DEV-2500

fix: Preview Env @milldr (#669)

what

• Checkout the preview branch for preview deployments

why

• The workflow runs on pull_request_target

references

• fix previews

♻️ chore(deps): update cloudposse/github-action-atmos-affected-stacks action to v4 @cloudpossebot (#667)

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

Datadog Landing page rewrite @Benbentwo (#662)

what

• Rewrite Datadog Landing page and clean it up

why

• Many parts of it are currently broken

references

• https://docs.cloudposse.com/layers/monitoring/datadog/
• https://pr-662.cloudposse-docs.ue2.dev.plat.cloudposse.org/layers/monitoring/datadog/

Fix Steps so that they always start at 1 @osterman (#668)

what

• Ensure the <Steps/> component sets the counter context
• Use the context for <StepNumber/>
• Fix formatting of philips labs setup
• Add missing <Steps/> container where necessary

why

• It was confusing that steps didn't start at 1, if multiple <Steps/> were defined on the page

v1.3.0

feat: Improve Identity Documentation @milldr (#665)

what

• Updated identity documentation
• Added mermaid diagrams

why

• Identity is a common point of confusing. We'd like to improve documentation
• Lucid is no longer supported internally. Instead we use mermaid

references

• customer

v1.2.0

Enhance Mermaid Diagrams and Definition Lists @osterman (#666)

what

• Improve formatting for mermaid diagrams
• Support icons in mermaid diagrams
• Automatic link terms in definition lists and support smooth scrolling to terms
• Update formatting for tutorials

why

• We're moving to use more mermaid diagrams because they are easier to main and searchable with algolia
• Using icons makes diagrams easier to digest and comparable to mainstream diagraming tools
• When there are a lot of definitions on a page, it's helpful to be able to link to a specific one

demo