Unable to destroy cluster

[dukarc]

Hi Folks,

We are still in our initial setup phase and are on the Deploy Clusters step for EKS.

We have deployed but would like to role back to get essentially a clean start here. Sadly we are hitting an issue with the destroy/cluster workflow. Wondering if we could get another set of eyes on this to help us.

Command:
atmos workflow destroy/cluster -f eks -s plat-usw2-dev

Results:

Destroying Targeted EKS Cluster
Proceed with caution!\n\n
Continue? (yes/no) yes
Continuing with EKS destruction...
WARN detected 'TF_PLUGIN_CACHE_DIR' set in the environment; this may interfere with Atmos's control of Terraform.

Initializing the backend...

Successfully configured the backend "s3"! OpenTofu will automatically
use this backend unless the backend configuration changes.
Initializing modules...
[Module initialization details redacted for brevity]

Initializing provider plugins...
[Provider initialization details redacted for brevity]

OpenTofu has been successfully initialized!
Switched to workspace "[REDACTED]".

[Module data reading details redacted for brevity]

Changes to Outputs:
  - hostname = "[REDACTED]" -> null

You can apply this plan to save these new output values to the OpenTofu state, without changing any real infrastructure.
╷
│ Warning: Value for undeclared variable
│ 
│ The root module does not declare a variable named "enable_alb_controller_ingress_group" but a value was found in file "[REDACTED].terraform.tfvars.json". If you meant to use this value, add a "variable" block to the
│ configuration.
│ 
│ To silence these warnings, use TF_VAR_... environment variables to provide certain "global" settings to all configurations in your organization. To reduce the verbosity of these warnings, use the -compact-warnings option.
╵
╷
│ Error: Attempt to get attribute from null value
│ 
│   on ../../account-map/modules/iam-roles/main.tf line 32, in locals:
│   32:   profiles_enabled = coalesce(var.profiles_enabled, local.account_map.profiles_enabled)
│     ├────────────────
│     │ local.account_map is null
│ 
│ This value is null, so it does not have any attributes.
╵
[Additional similar null value errors redacted for brevity]

Error 

exit status 1
Error 

Step 'step2' failed!
To resume the workflow from this step, run:
atmos workflow destroy/cluster -f eks --from-step step2

[cmarquezrusso]

I found the issue. atmos workflow destroy/cluster -f eks -s plat-usw2-dev assumes that the cluster and resources where deployed. In our configuration echo-server and the alb driver aren't working. The workaround is to ignore the error (as the component is not deployed/running and continue with the next step (defined on the eks workflow)