21 messages
π½οΈ
Michael Dizonalmost 4 years ago
what account should tfstate-backend be set up in?
Erik Osterman (Cloud Posse)almost 4 years ago
vendoring coming soon to atmos:
https://github.com/cloudposse/atmos/pull/145
https://github.com/cloudposse/atmos/pull/145
rssalmost 4 years ago(edited)
v1.4.12
what
Add atmos vendor commands
Add atmos vendor pull command
Improve error messages
Cleanup code
why
atmos vendor commands are used to manage vendoring for components and stacks
atmos vendor pull -c command pulls sources and mixins for the specified component
Support k8s-style YAML config (file component.yaml) to describe component vendoring configuration. The file is placed into the component folder and then the atmos command atmos vendor pull -c is executed to pull the sources and mixins...
what
Add atmos vendor commands
Add atmos vendor pull command
Improve error messages
Cleanup code
why
atmos vendor commands are used to manage vendoring for components and stacks
atmos vendor pull -c command pulls sources and mixins for the specified component
Support k8s-style YAML config (file component.yaml) to describe component vendoring configuration. The file is placed into the component folder and then the atmos command atmos vendor pull -c is executed to pull the sources and mixins...
rssalmost 4 years ago(edited)
v1.4.13
what
Improve error handling and error messages
Add atmos validate stacks command
why
Check and validate all YAML files in the stacks folder
Detect invalid YAML and print the file names and the line numbers
test
atmos validate stacks
Invalid YAML file 'catalog/invalid-yaml/invalid-yaml-1.yaml'
yaml: line 15: found unknown directive name
Invalid YAML file 'catalog/invalid-yaml/invalid-yaml-2.yaml'
yaml: line 16: could not find expected ':'
Invalid YAML file...
what
Improve error handling and error messages
Add atmos validate stacks command
why
Check and validate all YAML files in the stacks folder
Detect invalid YAML and print the file names and the line numbers
test
atmos validate stacks
Invalid YAML file 'catalog/invalid-yaml/invalid-yaml-1.yaml'
yaml: line 15: found unknown directive name
Invalid YAML file 'catalog/invalid-yaml/invalid-yaml-2.yaml'
yaml: line 16: could not find expected ':'
Invalid YAML file...
rssalmost 4 years ago(edited)
v1.4.14
what
Support terraform two-words commands
why
Support terraform workspace :
terraform workspace list
terraform workspace select
terraform workspace new
terraform workspace delete
terraform workspace show
references
https://www.terraform.io/cli/commands/workspace
test
atmos terraform workspace list test/test-component-override-3 -s tenant1-ue2-dev
Executing command:
/usr/local/bin/terraform workspace list
default...
what
Support terraform two-words commands
why
Support terraform workspace :
terraform workspace list
terraform workspace select
terraform workspace new
terraform workspace delete
terraform workspace show
references
https://www.terraform.io/cli/commands/workspace
test
atmos terraform workspace list test/test-component-override-3 -s tenant1-ue2-dev
Executing command:
/usr/local/bin/terraform workspace list
default...
Michael Dizonalmost 4 years ago
i'm running into an issue with
remote-state for the account-map component. i can run plan and deploy while authenticated with the root account, but when authenticated through the identity account, I run into this error Error: Error loading state error
β
β with module.iam_roles.module.account_map.data.terraform_remote_state.s3[0],
β on .terraform/modules/iam_roles.account_map/modules/remote-state/s3.tf line 8, in data "terraform_remote_state" "s3":
β 8: backend = "s3"
β
β error loading the remote state: failed to lock s3 state: 2 errors occurred:
β * ResourceNotFoundException: Requested resource not found
β * ResourceNotFoundException: Requested resource not found
βMichael Dizonalmost 4 years ago
while debugging, I pasted the
role_arn for a role in the account where the s3 bucket and dynamodb resources are located and everything worked fine.Michael Dizonalmost 4 years ago
from my stack config:
components:
terraform:
vpc:
backend_type: s3
remote_state_backend:
s3:
role_arn: arn:aws:iam::1234567890:role/namespace-environment-root-adminMichael Dizonalmost 4 years ago
it seems like the
utils_stack_config_yaml data component isn't pulling in the config, but i don't know how to debug/confirm what's happening
Matt Gowiealmost 4 years ago
Excited to see that docs site PR get merged. Let us know when itβs live!
rssalmost 4 years ago(edited)
v1.4.15
what
Various fixes and improvements
Better error handling and error messages
Improve validate stacks command
Improve describe stacks command
why
In this configuration
components:
terraform:
"test/test-component-override":
# The
# and points to the
component:...
what
Various fixes and improvements
Better error handling and error messages
Improve validate stacks command
Improve describe stacks command
why
In this configuration
components:
terraform:
"test/test-component-override":
# The
component attribute specifies that test/test-component-override inherits from the test/test-component base component,# and points to the
test/test-component Terraform component in the components/terraform foldercomponent:...
rssalmost 4 years ago(edited)
v1.4.16
what
Support {attributes} token in the components.helmfile.cluster_name_pattern CLI config
why
Allow using cluster_name_pattern in the following format {namespace}-{tenant}-{environment}-{stage}-{attributes}-eks-cluster (note that the tokens can be defined in any order)
When deploying multiple EKS clusters into the same AWS account and region, we can use attributes (blue, green, etc.) to be part of the EKS cluster names to name the clusters differently
test
// Define variables for a component...
what
Support {attributes} token in the components.helmfile.cluster_name_pattern CLI config
why
Allow using cluster_name_pattern in the following format {namespace}-{tenant}-{environment}-{stage}-{attributes}-eks-cluster (note that the tokens can be defined in any order)
When deploying multiple EKS clusters into the same AWS account and region, we can use attributes (blue, green, etc.) to be part of the EKS cluster names to name the clusters differently
test
// Define variables for a component...
rssover 3 years ago(edited)
v1.4.17
what
Improve atmos vendor pull command
Add more vendoring examples and tests
why
Show an example of vendoring a component with subfolders in the root folder (account-map with modules subfolder), and how to configure included_paths
test vendoring a component with modules subfolder
atmos vendor pull -c infra/account-map
Including 'README.md' since it matches the '*/.md' pattern from 'included_paths'
Including 'context.tf' since it matches the '*/.tf' pattern from 'included_paths'
Including...
what
Improve atmos vendor pull command
Add more vendoring examples and tests
why
Show an example of vendoring a component with subfolders in the root folder (account-map with modules subfolder), and how to configure included_paths
test vendoring a component with modules subfolder
atmos vendor pull -c infra/account-map
Including 'README.md' since it matches the '*/.md' pattern from 'included_paths'
Including 'context.tf' since it matches the '*/.tf' pattern from 'included_paths'
Including...
rssover 3 years ago
v1.4.17
what
Improve atmos vendor pull command
Add more vendoring examples and tests
why
Show an example of vendoring a component with subfolders in the root folder (account-map with modules subfolder), and how to configure included_paths
test vendoring a component with modules subfolder
atmos vendor pull -c infra/account-map
Including 'README.md' since it matches the '*/.md' pattern from 'included_paths'
Including 'context.tf' since it matches the '*/.tf' pattern from 'included_paths'
Including...
what
Improve atmos vendor pull command
Add more vendoring examples and tests
why
Show an example of vendoring a component with subfolders in the root folder (account-map with modules subfolder), and how to configure included_paths
test vendoring a component with modules subfolder
atmos vendor pull -c infra/account-map
Including 'README.md' since it matches the '*/.md' pattern from 'included_paths'
Including 'context.tf' since it matches the '*/.tf' pattern from 'included_paths'
Including...
rssover 3 years ago(edited)
v1.4.18
what
Update atmos workflow command
why
Allow specifying the stack for workflows on the command line
The stack defined on the command line (atmos workflow -f -s ) has the highest priority, it overrides all other stacks attributes
terraform-plan-all-test-components:
description: |
Run 'terraform plan' on 'test/test-component' and all its derived components.
The stack must be provided on the command line: atmos workflow terraform-plan-all-test-components -f workflow1 -s...
what
Update atmos workflow command
why
Allow specifying the stack for workflows on the command line
The stack defined on the command line (atmos workflow -f -s ) has the highest priority, it overrides all other stacks attributes
terraform-plan-all-test-components:
description: |
Run 'terraform plan' on 'test/test-component' and all its derived components.
The stack must be provided on the command line: atmos workflow terraform-plan-all-test-components -f workflow1 -s...
Cody Halovichover 3 years ago
I'm from Grizzly Force, we were a paying client back in the day well before Atmos, but I had updated everything to run in the atmos way
Cody Halovichover 3 years ago
I can no longer find a Dockerfile for atmos in your repo's
Cody Halovichover 3 years ago(edited)
actually, thats not correct, i've now grabbed the new Dockerfile from the atmos/examples/complete folder, it doesn't appear to reference variant at all. there's also no makefile though. i think i must have missed some critical changes.
Cody Halovichover 3 years ago(edited)
To make this easier, I have my components and my stacks, how do i get this to work quickly, I don't have time to be stalled. I use
{namespace}-{stage}-{name} for my ATMOS_STACKS_NAME_PATTERNCody Halovichover 3 years ago(edited)
i would like to use vendir to pull in my components from github
Cody Halovichover 3 years ago
β― ls
Permissions Size User Group Date Modified Name
.rw-r--r-- 3.4k cody cody 30 May 17:16 atmos.yaml
drwxr-xr-x - cody cody 30 May 17:15 components
.rw-r--r-- 1.2k cody cody 30 May 16:22 Dockerfile
drwxr-xr-x - cody cody 30 May 16:22 rootfs
drwxr-xr-x - cody cody 15 Mar 11:04 stacks
β― atmos terraform plan vpc -s ca1-dev
Searched all stack files, but could not find config for the component 'vpc' in the stack 'ca1-dev'.
Check that all attributes in the stack name pattern '{namespace}-{stage}-{name}' are defined in the stack config files.
Are the component and stack names correct? Did you forget an import?