Releases: cloudposse/docs
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
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
anddocs/components/library/aws/tgw/README.md
- Fix links referenced to renamed components
/components/library/aws/aws-sso
->/components/library/aws/identity-center
/components/library/aws/eks/karpenter/
->/components/library/aws/eks/karpenter-controller/
components/library/aws/datadog-configuration
->components/library/aws/datadog-credentials
/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
♻️ 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
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 thebearer-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]
usemake 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
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
withCollapsibleText
for all Software Delivery pages
why
- More obvious to readers to understand that you should click these examples
references
♻️ 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
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