Problem with cold start

[petabook]

Hello. I'm cold starting, and when I run atmos workflow init/tfstate -f baseline, I receive an error. The docs are unclear - which user should I use to execute the atmos commands during the initial setup? At this early stage, I only have the root user and the SuperAdmin IAM role in the org's root account.

$ atmos workflow init/tfstate -f baseline
<omitted for clarity>

Planning failed. OpenTofu encountered an error while generating this plan.

╷
│ Warning: Argument is deprecated
│ 
│   with aws_iam_role.default,
│   on iam.tf line 93, in resource "aws_iam_role" "default":
│   93:   managed_policy_arns = []
│ 
│ The managed_policy_arns argument is deprecated. Use the aws_iam_role_policy_attachment resource instead. If Terraform should exclusively manage
│ all managed policy attachments (the current behavior of this argument), use the aws_iam_role_policy_attachments_exclusive resource as well.
╵
╷
│ Error: Invalid provider configuration
│ 
│ Provider "registry.opentofu.org/cloudposse/awsutils" requires explicit configuration. Add a provider block to the root module and configure the
│ provider's required arguments as described in the provider documentation.
│ 
╵
╷
│ Error: failed to get shared config profile, qh-identity
│ 
│   with provider["registry.opentofu.org/hashicorp/aws"],
│   on providers.tf line 1, in provider "aws":
│    1: provider "aws" {
│ 
╵
╷
│ Error: error configuring Terraform AWS Provider: failed to get shared config profile, qh-identity
│ 
│   with provider["registry.opentofu.org/cloudposse/awsutils"],
│   on provider["registry.opentofu.org/cloudposse/awsutils"] with no configuration line 1:
│   (source code not available)
│ 
╵
exit status 1

Step 'step1' failed!

To resume the workflow from this step, run:
atmos workflow init/tfstate -f baseline --from-step step1

[GabisCampana]

@dudymas @milldr

[petabook]

Looking in stacks/workflows/baseline.yaml, the command that gets executed and fails is terraform deploy tfstate-backend -var=access_roles_enabled=false --stack core-use1-root --auto-generate-backend-file=false.

Running this command with debug enabled yields something that's beyond my pay grade :-)

atmos --logs-level=Debug terraform deploy tfstate-backend -var=access_roles_enabled=false --stack core-use1-root --auto-generate-backend-file=false
DEBU Found ENV var ATMOS_BASE_PATH=/workspace
DEBU processStoreConfig atmosConfig.StoresConfig=map[]
DEBU Found ENV var ATMOS_BASE_PATH=/workspace
DEBU processStoreConfig atmosConfig.StoresConfig=map[]
DEBU Found ENV var ATMOS_BASE_PATH=/workspace
DEBU Using command line argument '--auto-generate-backend-file=false'
DEBU processStoreConfig atmosConfig.StoresConfig=map[]
ERRO Could not find the component 'deploy' in the stack 'core-use1-root'.
Check that all the context variables are correctly defined in the stack manifests.
Are the component and stack names correct? Did you forget an import?

[petabook]

I'm trying to isolate the issue.
I created a new simple project with just one resource in it, and behold - I was able to recreate the problem I got cold starting the ref arch. Running atmos ... from within geodesic produces the following error.

│ Error: loading configuration: failed to get shared config profile, qh-identity                                                                    
│                                                                                                                                                   
│   with provider["registry.opentofu.org/hashicorp/aws"],                                                                                           
│   on providers.tf line 1, in provider "aws":                                                                                                      
│    1: provider "aws" {                                                                                                                            
│                                                                                                                                                   

Running atmos ... directly on the host works fine for the simple project. I haven't tested it yet for the ref arch.
So, it seems that the issue has something to do with my geodesic.