#atmos - December 2022

What is the difference between command and job when writing workflows?

How do i configure the planfile?

Hey all. Trying to learn Atmos. I think the tuorial here: https://docs.cloudposse.com/tutorials/atmos-getting-started/ is broken. I cloned the latest from <https://github.com/cloudposse/tutorials.git> and can follow through part of the tutorial (all the way through step 4). However, step 5 seems broken. When I try to run atmos workflow deploy-all -s example I get this error:

 ✗ . [none] (HOST) 02-atmos ⨠ atmos workflow deploy-all -s example
Error: required flag(s) "file" not set
Usage:
  atmos workflow [flags]

Flags:
      --dry-run        atmos workflow <name> -f <file> --dry-run
  -f, --file string    atmos workflow <name> -f <file>
  -h, --help           help for workflow
  -s, --stack string   atmos workflow <name> -f <file> -s <stack>

required flag(s) "file" not set

If I try to set the file I get this:

 ✗ . [none] (HOST) 02-atmos ⨠ atmos workflow deploy-all -s example -f example.yaml
file 'stacks/workflows/example.yaml' does not exist

It looks like atmos is expecting the workflow to be defined in a separate file (not in example.yaml). Is anyone else seeing this? I am doing something wrong?

v1.17.0
what
Add local search to atmos docs
Add atmos describe affected CLI command
Update docs website
why

Quickly search through documentation


The command atmos describe affected produces a list of the affected Atmos components and stacks given two Git commits. The command compares the final component sections (after all imports and deep-merging) for all Atmos components in all stacks, and produces a list of affected (changed) components in the stacks. The command also checks the changed files...

v1.17.0
what
Add local search to atmos docs
Add atmos describe affected CLI command
Update docs website
why

Quickly search through documentation


The command atmos describe affected produces a list of the affected Atmos components and stacks given two Git commits. The command compares the final component sections (after all imports and deep-merging) for all Atmos components in all stacks, and produces a list of affected (changed) components in the stacks. The command also checks the changed files...

v1.18.0
what
Update workflow commands of type shell
why
Workflow commands of type shell could be any complex shell commands (or scripts) in the workflow YAML definition file

v1.18.0
what
Update workflow commands of type shell
why
Workflow commands of type shell could be any complex shell commands (or scripts) in the workflow YAML definition file

@Andriy Knysh (Cloud Posse) having some issues with atmos describe affected

how do I deploy a multiregion component in atmos?

Hi there! I have a terraform project with complex tfvars variable of type "map of objects", which also contains nested maps of objects

{
 "complexvar":
	{
	  "toplevel": {
	    "objectA" : {
	      "bottomlevel1" : {
		    "attribute1": true
		    "attribute2": true
	      },
	      "bottomlevel2" : {
		    "attribute1": true
		    "attribute2": true
	      }
	    },
	    "objectB" : {
	      "bottomlevel3" : {
		    "attribute1": "abc"
		    "attribute2": "abc"
	      }
	    }
	  }
	}
}

and I am trying to update attributes of "bottomlevel*" objects with "vars" property of the stack:

vars:
  complexvar:
    objectA:
      bottomlevel1: 
        attribute1: false

When I do following, atmos generates a new tfvars.json only with bottomlevel1 object and removes bottomlevel2 and objectB instead of deep merge. Does atmos support deep merge of terraform.tfvars.json and stack vars?

v1.19.0
what
Add Sources of Component Variables to atmos describe component command
Update docs
why
The atmos describe component command outputs the final deep-merged component configuration in YAML format.
The output contains the following sections:
atmos_component - Atmos component name
atmos_stack - Atmos stack name
backend - Terraform backend configuration
backend_type - Terraform backend type
command - the binary to execute when provisioning the component (e.g. terraform, terraform-1, helmfile)...

Hi all, since backend.tf.json files need to be generated when 'vendoring' components from terraform-aws-components, why would atmos users leave auto_generate_backend_file: false and generate backend files manually?