LocalStack Manual cold start issue - deploy/account-settings fails

[petabook]

I'm trying to manually perform a cold start with LocalStack. I've made some progress, but I've encountered an issue. I'm currently trying to run atmos workflow deploy/account-settings -f accounts, but it fails:

│ Error: Invalid index
│ 
│   on ../account-map/modules/iam-roles/main.tf line 46, in locals:
│   46:   is_root_user   = local.current_identity_account == local.account_map.full_account_map[local.root_account_name]
│     ├────────────────
│     │ local.account_map.full_account_map is object with 12 attributes
│     │ local.root_account_name is "core-root"
│ 
│ The given key does not identify an element in this collection value.

Tracing what full_account_map has in it, I found that indeed it doesn't have an element named core-root, but instead an element named master.

$ atmos terraform output account-map -s core-gbl-root | grep -A13 full_account_map

full_account_map = {
  "core-artifacts" = "585534971824"
  "core-audit" = "787971408309"
  "core-auto" = "730716181603"
  "core-dns" = "968742829426"
  "core-identity" = "340829543332"
  "core-network" = "682803573764"
  "core-security" = "143738600204"
  "master" = "324037278566"
  "plat-dev" = "758867506365"
  "plat-prod" = "909243139744"
  "plat-sandbox" = "260461318034"
  "plat-staging" = "336302417760"
}

Any idea?

[milldr]

I believe this is the same issue as this discussion:
https://github.com/orgs/cloudposse/discussions/20#discussioncomment-10909522

Please try setting root_account_aws_name and see if that works

[petabook]

Thanks, but root_account_aws_name etc. is already set correctly in my stacks/catalog/account-map.yaml.
I guess it's something else that is happening here.

[petabook]

It turns out that on LocalStack, when creating an organization the management account name becomes master. And so setting root_account_aws_name: master in stacks/catalog/account-map.yaml solves the issue.