#atmos - July 2023

v1.39.0
what
Make Atmos understand Terraform configurations and dependencies
Update atmos describe component command
Update atmos describe affected command
Add Atmos custom commands to atmos.yaml
Update docs for atmos describe component and atmos describe affected commands
why

Atmos now understands Terraform configurations and dependencies! (using a Terraform parser from HashiCorp) This is useful to detect component dependencies when a Terraform component in the components/terraform folder uses...

@Andriy Knysh (Cloud Posse), on #office-hours, @Hans D shared he is dabbling with Cuelang to generate atmos configs

v1.40.0
what
Documentation pages for GitHub Actions for Terraform Plan and Apply
why
Documented the two new GitHub actions for Terraform Plan and Apply

Hey folks -- How did the Atmos + Atlantis support end up turning out? Are there any users of that workflow? @PePe Amengual maybe you?

We have a project coming up where the client is set on using Terragrunt. We were going to just accept that and use Atlantis with them so we didn't need to write TF pipes, but now we're finding out TG + Atlantis isn't really that great of a combo? So I'm wondering if we can push them in another direction on the TF framework side, but wanted some more info on how Atlantis is working with Atmos.

v1.40.0
what
Documentation pages for GitHub Actions for Terraform Plan and Apply
why
Documented the two new GitHub actions for Terraform Plan and Apply

Hey all, I m trying to create admin stack for spacelift and getting this error message:

│ Error: the stack name pattern '{tenant}-{environment}-{stage}' specifies 'tenant`, but the stack 'catalog/account' does not have a tenant defined in the stack file 'catalog/account'
│ 
│   with module.child_stacks_config.module.spacelift_config.data.utils_spacelift_stack_config.spacelift_stacks,
│   on .terraform/modules/child_stacks_config.spacelift_config/modules/spacelift/main.tf line 1, in data "utils_spacelift_stack_config" "spacelift_stacks":
│    1: data "utils_spacelift_stack_config" "spacelift_stacks" {

I m running my command in geodesic container locally:

atmos terraform apply spacelift/admin-stack -s core-gbl-auto

Also, my file structure is like this :

stacks
   catalog
   core
   infra
   mixins

Any help will be highly appreciated!

Hi Team,, I am looking for 1 help about atmos tool. We are seeing that some tag name change through spacelift for drift detection.. My question was how to know where the values are passing to it..
My question is like where the value syca-plat-use2-dev in the below example comes from.. any pointers is helpful

 # module.store_write.aws_ssm_parameter.default["/platform/syca-plat-use2-dev-eks-cluster/_metadata/kube_version"] will be updated in-place
  ~ resource "aws_ssm_parameter" "default" {
        id          = "/platform/syca-plat-use2-dev-eks-cluster/_metadata/kube_version"
        name        = "/platform/syca-plat-use2-dev-eks-cluster/_metadata/kube_version"
      ~ tags        = {
            "Environment" = "xx"
          ~ "Name"        = "syca-plat-use2-dev" -> "syca-plat-use2-dev-platform"
            "Namespace"   = "xx"
            "Stage"       = "xx"
            "Tenant"      = "xx"
        }
      ~ tags_all    = {
          ~ "Name"        = "syca-plat-use2-dev" -> "syca-plat-use2-dev-platform"
            # (4 unchanged elements hidden)
        }
        # (9 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

is there a way to template a workflow ?to have it rendered before it is run

How do you guys are managing the interface for custom policies being pass as inputs in Atmos? I just do not like much the fact users need to pass this huge blob of text in the stack, I’m trying to think how to organize it

v1.41.0
what
Add exampes and tests for validation of components with multiple hierarchical inheritance
why

Show that the settings.validation section is inherited all the way down the inheritance chain, even when using multiple abstract bae components, and atmos validate component command executes the validation policies placed at any level of the inheritance hierarchy
base-component-1 is an abstract component, and it has the settings.validation section defined using an OPA policy
base-component-3 is...

v1.41.0
what
Add exampes and tests for validation of components with multiple hierarchical inheritance
why

Show that the settings.validation section is inherited all the way down the inheritance chain, even when using multiple abstract bae components, and atmos validate component command executes the validation policies placed at any level of the inheritance hierarchy
base-component-1 is an abstract component, and it has the settings.validation section defined using an OPA policy
base-component-3 is...

Is it possible to rename files when vendoring? I know it is possible via mixins . How can it be done via source?

@Erik Osterman (Cloud Posse) I was watching the office hours and I hear the question about monorepo modules 🧵

v1.42.0
what
Add Sprig functions to Atmos Go templates in imports
Various fixes and improvements for atmos describe component and component dependencies calculation
Update docs https://atmos.tools/cli/commands/describe/component/
why

Sprig functions in Atmos Go templates in imports provide...

v1.42.0
what
Add Sprig functions to Atmos Go templates in imports
Various fixes and improvements for atmos describe component and component dependencies calculation
Update docs https://atmos.tools/cli/commands/describe/component/
why

Sprig functions in Atmos Go templates in imports provide...