docs: proposal to replace CodePipeline with CloudFormation stacks - #689
docs: proposal to replace CodePipeline with CloudFormation stacks#689jmelis wants to merge 1 commit into
Conversation
Covers the three pillars: internal repo owns all account infra, CloudFormation stacks for RC/MC provisioning, and MC Autoscaler for stable environments. Includes developer flow analysis and migration strategy. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/jira-refresh |
|
|
||
| | Option | How It Works | Pros | Cons | | ||
| | --- | --- | --- | --- | | ||
| | **Terraform Cloud** | Workspaces per cluster, VCS-triggered or API-driven runs | Managed state, plan/apply UI, team workflows, native GitHub integration | Cost per workspace, external dependency, network access to private resources | |
There was a problem hiding this comment.
Is fedRAMP being considered here?
Summary
rosa-hyperfleet-internal) expands to own all account-level infrastructure across all environmentsOpen questions for the team
🤖 Generated with Claude Code