#refarch - May 2025

Hi guys,
We managed to get ssosync up and running, and we also finished with the networking layer

We are now looking into adding GitHub integration (OIDC + managed runners using runs-on.com as you suggested)

While deploying github-oidc-provider, I got this warning:

 The root module does not declare a variable named "enabled" but a value was found in file
│ "plat-gbl-dev-github-oidc-provider.terraform.tfvars.json". If you meant to use this value, add a "variable" block to
│ the configuration.

This plan has no changes:

No changes. Your infrastructure matches the configuration.

This happens for both commands:
• atmos terraform plan github-oidc-provider --stack core-gbl-identity
• atmos terraform plan github-oidc-provider --stack plat-gbl-dev
I tried several ways to ensure that variable is present, from adding enabled=true on several places under catalog/github-oidc-provider.yaml to adding them into components/terraform/aws-github-oidc-provider/variables.tfand even hardcoding components/terraform/aws-github-oidc-provider/main.tf None of those attempts worked.

I also added the vars for Superadmin = true, but I am still getting the same outcome: no changes to be made.

Could you please point us on the right direction?

TIA

cc @Cyrus Dukart

Hi guys,

We are deploying eks clusters following https://docs.cloudposse.com/layers/eks/deploy-clusters/
We are finding issues when running

atmos workflow vendor -f eks

The error message is:

INFO Vendoring from 'vendor.yaml'
 Error 

the flag '--component' is passed, but the component is not defined in any of the 'sources' in the vendor config file and the imports component 'iam-service-linked-roles', file 'vendor.yaml'
 Error 

Step 'step1' failed!
To resume the workflow from this step, run:
atmos workflow vendor -f eks --from-step step1

I can see that the tarball included:
• components/terraform/eks
• stacks/catalog/eks
• workflows/eks
I think there are missing parameters on vendor.yaml, but I couldnt find the right terraform module in cloudposse repo for this.

Should be use aws-eks-cluster instead? Or should we configure the vendor to read local files and not pull anything?

Hi everyone — to reduce confusion and provide more focused support for our commercial reference architecture, we’ll be closing this channel. For future questions or requests, please visit cloudposse.com/support. Thanks for your understanding!

archived the channel