21 messages
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
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)...
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...
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...
rssalmost 4 years ago(edited)
v1.7.0
Add load_balancing_algorithm_type input variable @linhkikuchi (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1496538757" data-permission-text="Title is private"...
Add load_balancing_algorithm_type input variable @linhkikuchi (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1496538757" data-permission-text="Title is private"...
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.7.0
fix(modules/git/bootstrap): remove lazy assignments @dudymas (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1531472014" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/335"...
fix(modules/git/bootstrap): remove lazy assignments @dudymas (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1531472014" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/335"...
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":...
rssalmost 4 years ago(edited)
v1.8.0
fix(Makefile): no longer recursively set OS @dudymas (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1550109634" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/336"...
fix(Makefile): no longer recursively set OS @dudymas (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1550109634" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/336"...
rssalmost 4 years ago(edited)
v1.9.0
[helm] Update repo endpoints @goruha (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1553149739" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/337" data-hovercard-type="pull_request"...
[helm] Update repo endpoints @goruha (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1553149739" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/337" data-hovercard-type="pull_request"...
rssalmost 4 years ago(edited)
v1.10.0
Added docs support for github actions reusable workflows @goruha (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1510180540" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/334"...
Added docs support for github actions reusable workflows @goruha (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1510180540" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/334"...
rssalmost 4 years ago(edited)
v1.8.0 Update Alpine v3.16.3 - v3.17.1>
Update alpine Docker tag to v3.17.1 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1460754589" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/817"...
Update alpine Docker tag to v3.17.1 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1460754589" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/817"...
rssalmost 4 years ago(edited)
v0.73.0
DEV-289: Tutorial Revamp @milldr (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1401681373" data-permission-text="Title is private" data-url="https://github.com/cloudposse/docs/issues/543" data-hovercard-type="pull_request"...
DEV-289: Tutorial Revamp @milldr (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1401681373" data-permission-text="Title is private" data-url="https://github.com/cloudposse/docs/issues/543" data-hovercard-type="pull_request"...
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...