19 messages
👽️
rssalmost 4 years ago(edited)
v1.19.1
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)...
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)...
rssalmost 4 years ago
v1.19.1
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)...
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)...
Viacheslavalmost 4 years ago
Hi all! I have an atmos workflow that creates two stacks with terraform. Let suppose, stack1 creates an Azure resource group with randomly generated name, and stack2 creates a storage account that needs to be pointed to that resource group. In order to create a storage account, I need to use a data source for the resource group in stack2, but I don't know the name of that resource group to import.
Is there any native way to read outputs from stack1 and pass it as variables to stack2? I want to avoid using some complex bash commands between applying two stacks. Maybe there are any other suitable approaches to solve this problem following the philosophy of atmos?
Is there any native way to read outputs from stack1 and pass it as variables to stack2? I want to avoid using some complex bash commands between applying two stacks. Maybe there are any other suitable approaches to solve this problem following the philosophy of atmos?
rssalmost 4 years ago(edited)
v1.20.0
what & why
Add "Quick Start" doc https://atmos.tools/category/quick-start/
Add "Component Remote State" docs https://atmos.tools/core-concepts/components/remote-state/
Add "CLI Commands Cheat Sheet" doc https://atmos.tools/cli/cheatsheet/
Update/improve "Atmos...
what & why
Add "Quick Start" doc https://atmos.tools/category/quick-start/
Add "Component Remote State" docs https://atmos.tools/core-concepts/components/remote-state/
Add "CLI Commands Cheat Sheet" doc https://atmos.tools/cli/cheatsheet/
Update/improve "Atmos...
rssalmost 4 years ago
v1.20.0
what & why
Add "Quick Start" doc https://atmos.tools/category/quick-start/
Add "Component Remote State" docs https://atmos.tools/core-concepts/components/remote-state/
Add "CLI Commands Cheat Sheet" doc https://atmos.tools/cli/cheatsheet/
Update/improve "Atmos...
what & why
Add "Quick Start" doc https://atmos.tools/category/quick-start/
Add "Component Remote State" docs https://atmos.tools/core-concepts/components/remote-state/
Add "CLI Commands Cheat Sheet" doc https://atmos.tools/cli/cheatsheet/
Update/improve "Atmos...
PePe Amengualalmost 4 years ago(edited)
Hi, I see some action in this repo https://github.com/cloudposse/github-action-setup-atmos is this action ready to use? @Matt Calhoun
rssalmost 4 years ago(edited)
v1.21.0
what
Avoid exiting early when missing configuration file
Make the --workflow-template flag optional for the atmos atlantis generate repo-config command. Update docs
Update atmos describe stacks and atmos describe affected commands
why
Do not immediately exit when a configuration file is not found. This allows, for example, the version command to be run without a configuration file. The commands requiring a configuration file still do exit when it is missing. See <a class="issue-link...
what
Avoid exiting early when missing configuration file
Make the --workflow-template flag optional for the atmos atlantis generate repo-config command. Update docs
Update atmos describe stacks and atmos describe affected commands
why
Do not immediately exit when a configuration file is not found. This allows, for example, the version command to be run without a configuration file. The commands requiring a configuration file still do exit when it is missing. See <a class="issue-link...
rssalmost 4 years ago
v1.21.0
what
Avoid exiting early when missing configuration file
Make the --workflow-template flag optional for the atmos atlantis generate repo-config command. Update docs
Update atmos describe stacks and atmos describe affected commands
why
Do not immediately exit when a configuration file is not found. This allows, for example, the version command to be run without a configuration file. The commands requiring a configuration file still do exit when it is missing. See <a class="issue-link...
what
Avoid exiting early when missing configuration file
Make the --workflow-template flag optional for the atmos atlantis generate repo-config command. Update docs
Update atmos describe stacks and atmos describe affected commands
why
Do not immediately exit when a configuration file is not found. This allows, for example, the version command to be run without a configuration file. The commands requiring a configuration file still do exit when it is missing. See <a class="issue-link...
Geoffrey Hichbornalmost 4 years ago
Hello all, I have (what I hope is) a fairly basic question about Atmos that I haven't been able to answer with the documentation. Is there a way to configure components in a stack, such that you can take outputs from one component and feed them in as inputs to another component?
rssalmost 4 years ago(edited)
v1.22.0
what
Update atmos workflow command to allow restarting workflows from a named step
Update workflow docs https://atmos.tools/core-concepts/workflows/
why
Useful when you want to restart a workflow from a particular step.
Each workflow step can be given an arbitrary name (step's identifier) using the name attribute. For example:
workflows:
test-1:
description: "Test workflow"
steps:
- command: echo Command...
what
Update atmos workflow command to allow restarting workflows from a named step
Update workflow docs https://atmos.tools/core-concepts/workflows/
why
Useful when you want to restart a workflow from a particular step.
Each workflow step can be given an arbitrary name (step's identifier) using the name attribute. For example:
workflows:
test-1:
description: "Test workflow"
steps:
- command: echo Command...
rssalmost 4 years ago
v1.22.0
what
Update atmos workflow command to allow restarting workflows from a named step
Update workflow docs https://atmos.tools/core-concepts/workflows/
why
Useful when you want to restart a workflow from a particular step.
Each workflow step can be given an arbitrary name (step's identifier) using the name attribute. For example:
workflows:
test-1:
description: "Test workflow"
steps:
- command: echo Command...
what
Update atmos workflow command to allow restarting workflows from a named step
Update workflow docs https://atmos.tools/core-concepts/workflows/
why
Useful when you want to restart a workflow from a particular step.
Each workflow step can be given an arbitrary name (step's identifier) using the name attribute. For example:
workflows:
test-1:
description: "Test workflow"
steps:
- command: echo Command...
rssalmost 4 years ago(edited)
v1.23.0
what
Update atmos terraform apply and atmos terraform deploy commands
Add --planfile flag to atmos terraform apply and atmos terraform deploy commands
Improve docs
why
Support two ways of specifying a planfile for atmos terraform apply and atmos terraform deploy commands:
atmos terraform apply and atmos terraform deploy commands support --planfile flag to specify the path to a planfile. The --planfile flag should be used instead of the planfile argument in the native terraform apply...
what
Update atmos terraform apply and atmos terraform deploy commands
Add --planfile flag to atmos terraform apply and atmos terraform deploy commands
Improve docs
why
Support two ways of specifying a planfile for atmos terraform apply and atmos terraform deploy commands:
atmos terraform apply and atmos terraform deploy commands support --planfile flag to specify the path to a planfile. The --planfile flag should be used instead of the planfile argument in the native terraform apply...
rssalmost 4 years ago
v1.23.0
what
Update atmos terraform apply and atmos terraform deploy commands
Add --planfile flag to atmos terraform apply and atmos terraform deploy commands
Improve docs
why
Support two ways of specifying a planfile for atmos terraform apply and atmos terraform deploy commands:
atmos terraform apply and atmos terraform deploy commands support --planfile flag to specify the path to a planfile. The --planfile flag should be used instead of the planfile argument in the native terraform apply...
what
Update atmos terraform apply and atmos terraform deploy commands
Add --planfile flag to atmos terraform apply and atmos terraform deploy commands
Improve docs
why
Support two ways of specifying a planfile for atmos terraform apply and atmos terraform deploy commands:
atmos terraform apply and atmos terraform deploy commands support --planfile flag to specify the path to a planfile. The --planfile flag should be used instead of the planfile argument in the native terraform apply...
rssalmost 4 years ago(edited)
v1.24.0
what & why
Update atmos describe affected command
Add affected Spacelift stack to each item in the output list (if the Spacelift workspace is enabled in settings.spacelift.workspace_enabled for the component in the stack). This takes into account settings.spacelift.stack_name and settings.spacelift.stack_name_pattern settings which override the auto-generated Spacelift stack names
[
{
"component": "test/test-component-override-2",
"component_type":...
what & why
Update atmos describe affected command
Add affected Spacelift stack to each item in the output list (if the Spacelift workspace is enabled in settings.spacelift.workspace_enabled for the component in the stack). This takes into account settings.spacelift.stack_name and settings.spacelift.stack_name_pattern settings which override the auto-generated Spacelift stack names
atmos describe afected
[
{
"component": "test/test-component-override-2",
"component_type":...
rssalmost 4 years ago
v1.24.0
what & why
Update atmos describe affected command
Add affected Spacelift stack to each item in the output list (if the Spacelift workspace is enabled in settings.spacelift.workspace_enabled for the component in the stack). This takes into account settings.spacelift.stack_name and settings.spacelift.stack_name_pattern settings which override the auto-generated Spacelift stack names
[
{
"component": "test/test-component-override-2",
"component_type":...
what & why
Update atmos describe affected command
Add affected Spacelift stack to each item in the output list (if the Spacelift workspace is enabled in settings.spacelift.workspace_enabled for the component in the stack). This takes into account settings.spacelift.stack_name and settings.spacelift.stack_name_pattern settings which override the auto-generated Spacelift stack names
atmos describe afected
[
{
"component": "test/test-component-override-2",
"component_type":...
Nimesh Aminalmost 4 years ago(edited)
hi! When I try to run atmos terraform shell <component> -s <env>
I get: "can't find a shell to execute" at the very end.
I remember this working at some point, but now I'm second guessing myself 😕
This is all within the docker container. Am I forgetting to set some env?
I get: "can't find a shell to execute" at the very end.
I remember this working at some point, but now I'm second guessing myself 😕
This is all within the docker container. Am I forgetting to set some env?
Russell Shermanalmost 4 years ago
it appears that the atmos helmfile implementation does not not take into account the possibility of an eks cluster name including attributes
adding attributes to the cluster_name_pattern does not appear to have any effect
and there does not appear to be a way to override or specify the cluster name
am i missing something?
adding attributes to the cluster_name_pattern does not appear to have any effect
and there does not appear to be a way to override or specify the cluster name
am i missing something?
PePe Amengualalmost 4 years ago(edited)
How do you guys deploy lambdas with atmos? I’m trying to decide the best way when I have a monorepo with atmos infra and another repo for the lambda code and trying to avoid 2 PRs to create/deploy the lambda function
rssalmost 4 years ago(edited)
v1.25.0
what
Update Atmos Stack imports
Update docs https://atmos.tools/core-concepts/stacks/imports/
Add imports schema with context
Allow using Go templates in imported configurations
why
Auto-generate Atmos components from templates
Using imports with context and parameterized config files will help to make the stack configurations extremely DRY,
and is very useful when creating stacks and components for <a...
what
Update Atmos Stack imports
Update docs https://atmos.tools/core-concepts/stacks/imports/
Add imports schema with context
Allow using Go templates in imported configurations
why
Auto-generate Atmos components from templates
Using imports with context and parameterized config files will help to make the stack configurations extremely DRY,
and is very useful when creating stacks and components for <a...