Open
Conversation
New blog post explaining how to migrate components to use Atmos Auth and the next-generation authentication approach, including practical guidance on using Atmos mixins to update any component regardless of version. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Add "Why We Made These Changes" section explaining testability as the driving force, and an info callout clarifying that all components remain usable during the transition with providers.tf as the version indicator. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restructure the blog post into two distinct migration paths: 1. Upgrading legacy infrastructure to Atmos Auth (forward migration) 2. Using new component versions on legacy infrastructure (bridge strategy) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…version Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add decision table for guide selection, Atmos Auth prerequisites, precise generation definition, failure modes with sample errors, Terraform state impact notes, CI/CD runner guidance, expanded verification checklist, and dummy iam_roles module explanation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…n snippet Note that cold start components have always used simple providers. Add iam_role_arn_templates to the static account map example. Remove standalone provider snippet from next-gen section. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Show how to use terraform.generate in stack config as an alternative to per-component mixins, including versions_override.tf for migration. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
why
references