skills.rest
cloudposse
cloudposseOFFICIAL
Explore all skills by this author →
Website𝕏@cloudposseGitHub

account-map-migration

Migrate legacy account-map remote-state lookups to a static account_map variable.

98|34|Updated Apr 27, 2018
Search Tags:#migrate#provider-configuration#remote-state#atmos#account-map#static-account-map#defaults.yaml
One-click install
npx skills add https://github.com/cloudposse/docs --skill account-map-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: account-map-migration
Source: https://github.com/cloudposse/docs/tree/main/examples/snippets/.claude/skills/account-map-migration
Command: npx skills add https://github.com/cloudposse/docs --skill account-map-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy account-map usage from dynamic lookups to a static account_map variable, simplifying provider configuration and removing remote-state dependencies.

Core Features & Use Cases

  • Migrates component patterns from account-map remote-state to a static account_map defined in stacks/orgs/acme/_defaults.yaml.
  • Removes remote-state lookups by vendor-ing a static provider configuration and updating defaults.
  • Supports ongoing migrations by documenting a clear pattern and bypass mechanism for account-map lookups.

Quick Start

Run the migration workflow to replace dynamic account-map lookups with a static account_map and update provider configurations.

Frequently Asked Questions about account-map-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from dynamic account-map remote-state lookups to a static configuration?▼

To migrate from dynamic account-map remote-state lookups, replace the dynamic lookups with a static account_map variable. This simplifies provider configuration and removes remote-state dependencies.

What is the best way to remove remote-state dependencies from legacy account-map usage?▼

Removing remote-state dependencies from legacy account-map usage is achieved by vendoring a static provider configuration. This bypasses the need for dynamic lookups during deployment.

Where do I define static defaults when migrating away from account-map remote-state?▼

Static defaults are defined in stacks/orgs/acme/_defaults.yaml when migrating away from account-map remote-state. This file houses the static account_map variable.

Can I use a static account_map to simplify provider configuration in atmos?▼

Yes, using a static account_map simplifies provider configuration in atmos. It replaces dynamic account-map remote-state lookups with vendored static configurations.

Why does my component still rely on account-map remote-state after updating defaults.yaml?▼

Components still rely on account-map remote-state if providers.tf is not vendored. Vendoring providers.tf is required to remove the remote-state dependencies completely.

Does migrating to a static account_map require updating the vendored provider configuration?▼

Yes, migrating to a static account_map requires updating the vendored provider configuration. This ensures providers.tf no longer references remote-state dependencies.

Related Skills

Explore More Software Engineering Skills→
cloudpossecloudposse
98

debugging-atmos

Troubleshoot Atmos configuration and deployment issues with verbose logging and stack inspection.

Official
Intermediate
FernanSuozaFernanSuoza

infra-terraform-infrastructure-as-code

Design and validate Terraform infrastructure configurations with version pinning and plan review.

Community
Advanced
cloudpossecloudposse
98

developing-stacks

Guide Atmos stack YAML usage for reproducible infrastructure deployments.

Official
Advanced
infraspecdevinfraspecdev
3

atmos-component-hygiene

Detect hygiene issues in Atmos Terraform components during creation and pull request review.

Official
Intermediate