39 messages
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
rssover 3 years ago(edited)
v1.11.0
what
Add disabled field to component validation steps
Add verbose field to custom command steps
Expose component config in custom commands
why
Add disabled field to component validation steps to be able to to skip the validation step. disabled is set to false by default and the validation step is allowed if disabled attribute is not specified. This is useful when we add component validation in settings.validation at environment/tenant/stage/base component level, but we want to disable...
what
Add disabled field to component validation steps
Add verbose field to custom command steps
Expose component config in custom commands
why
Add disabled field to component validation steps to be able to to skip the validation step. disabled is set to false by default and the validation step is allowed if disabled attribute is not specified. This is useful when we add component validation in settings.validation at environment/tenant/stage/base component level, but we want to disable...
rssover 3 years ago
v1.11.0
what
Add disabled field to component validation steps
Add verbose field to custom command steps
Expose component config in custom commands
why
Add disabled field to component validation steps to be able to to skip the validation step. disabled is set to false by default and the validation step is allowed if disabled attribute is not specified. This is useful when we add component validation in settings.validation at environment/tenant/stage/base component level, but we want to disable...
what
Add disabled field to component validation steps
Add verbose field to custom command steps
Expose component config in custom commands
why
Add disabled field to component validation steps to be able to to skip the validation step. disabled is set to false by default and the validation step is allowed if disabled attribute is not specified. This is useful when we add component validation in settings.validation at environment/tenant/stage/base component level, but we want to disable...
rssover 3 years ago(edited)
v1.11.1
what
Update custom commands
Refactor custom commands code
why
When parsing and executing CLI custom commands, clone the command struct into a local variable because of the automatic closure in the Run function of the Cobra command (the last processed command config affects all the previous ones). Cloning will make a closure over the local variable which is different in each iteration (we cloned just Go slices before, but we need to clone Go maps as well, so we clone the whole struct instead)
what
Update custom commands
Refactor custom commands code
why
When parsing and executing CLI custom commands, clone the command struct into a local variable because of the automatic closure in the Run function of the Cobra command (the last processed command config affects all the previous ones). Cloning will make a closure over the local variable which is different in each iteration (we cloned just Go slices before, but we need to clone Go maps as well, so we clone the whole struct instead)
rssover 3 years ago
v1.11.1
what
Update custom commands
Refactor custom commands code
why
When parsing and executing CLI custom commands, clone the command struct into a local variable because of the automatic closure in the Run function of the Cobra command (the last processed command config affects all the previous ones). Cloning will make a closure over the local variable which is different in each iteration (we cloned just Go slices before, but we need to clone Go maps as well, so we clone the whole struct instead)
what
Update custom commands
Refactor custom commands code
why
When parsing and executing CLI custom commands, clone the command struct into a local variable because of the automatic closure in the Run function of the Cobra command (the last processed command config affects all the previous ones). Cloning will make a closure over the local variable which is different in each iteration (we cloned just Go slices before, but we need to clone Go maps as well, so we clone the whole struct instead)
rssover 3 years ago(edited)
v1.11.2
what
Update parsing command-line arguments
why
After refactoring in atmos v1.10.x, the command-line arguments were parsed incorrectly. For example, in the following command
atmos terraform plan -s --auto-generate-backend-file=true
the argument --auto-generate-backend-file=true was lost and never applied.
what
Update parsing command-line arguments
why
After refactoring in atmos v1.10.x, the command-line arguments were parsed incorrectly. For example, in the following command
atmos terraform plan -s --auto-generate-backend-file=true
the argument --auto-generate-backend-file=true was lost and never applied.
rssover 3 years ago
v1.11.2
what
Update parsing command-line arguments
why
After refactoring in atmos v1.10.x, the command-line arguments were parsed incorrectly. For example, in the following command
atmos terraform plan -s --auto-generate-backend-file=true
the argument --auto-generate-backend-file=true was lost and never applied.
what
Update parsing command-line arguments
why
After refactoring in atmos v1.10.x, the command-line arguments were parsed incorrectly. For example, in the following command
atmos terraform plan -s --auto-generate-backend-file=true
the argument --auto-generate-backend-file=true was lost and never applied.
rssover 3 years ago(edited)
v1.11.3
what
Fix atmos vendor pull command
why
The function os.IsNotExist has probably changed in some latest Go versions
After calling os.Stat, don't check for "path does not exist" errors using os.IsNotExist, instead check for all errors
This fixes the error:
atmos vendor pull -c acm
Pulling sources for the component 'acm' from
'/localhost/infra/components/terraform/acm/github.com/cloudposse/terraform-aws-components.git/modules/acm?ref=1.86.0'
and writing to...
what
Fix atmos vendor pull command
why
The function os.IsNotExist has probably changed in some latest Go versions
After calling os.Stat, don't check for "path does not exist" errors using os.IsNotExist, instead check for all errors
This fixes the error:
atmos vendor pull -c acm
Pulling sources for the component 'acm' from
'/localhost/infra/components/terraform/acm/github.com/cloudposse/terraform-aws-components.git/modules/acm?ref=1.86.0'
and writing to...
rssover 3 years ago
v1.11.3
what
Fix atmos vendor pull command
why
The function os.IsNotExist has probably changed in some latest Go versions
After calling os.Stat, don't check for "path does not exist" errors using os.IsNotExist, instead check for all errors
This fixes the error:
atmos vendor pull -c acm
Pulling sources for the component 'acm' from
'/localhost/infra/components/terraform/acm/github.com/cloudposse/terraform-aws-components.git/modules/acm?ref=1.86.0'
and writing to...
what
Fix atmos vendor pull command
why
The function os.IsNotExist has probably changed in some latest Go versions
After calling os.Stat, don't check for "path does not exist" errors using os.IsNotExist, instead check for all errors
This fixes the error:
atmos vendor pull -c acm
Pulling sources for the component 'acm' from
'/localhost/infra/components/terraform/acm/github.com/cloudposse/terraform-aws-components.git/modules/acm?ref=1.86.0'
and writing to...
rssover 3 years ago(edited)
v1.12.0
what
Update atmos custom commands
Update atmos terraform generate backends command
why
Update atmos custom commands to allow the command's ENV var values to have access to {{ .ComponentConfig.xxx.yyy.zzz }} Go template variables. If a custom command defines component_config section with component and stack, atmos generates the config for the component in the stack and makes it available in {{ .ComponentConfig.xxx.yyy.zzz }} Go template variables, exposing all the component sections. This is...
what
Update atmos custom commands
Update atmos terraform generate backends command
why
Update atmos custom commands to allow the command's ENV var values to have access to {{ .ComponentConfig.xxx.yyy.zzz }} Go template variables. If a custom command defines component_config section with component and stack, atmos generates the config for the component in the stack and makes it available in {{ .ComponentConfig.xxx.yyy.zzz }} Go template variables, exposing all the component sections. This is...
rssover 3 years ago(edited)
v1.12.1
what
Update atmos atlantis generate repo-config command
why
If an atmos component is derived from a base component, terraform workspace is calculated differently:
for a regular atmos component, terraform workspace is the stack name (e.g. tenant1-ue2-prod)
for a derived atmos component, terraform workspace is stack name + component name (e.g. tenant1-ue2-prod-)
For example, for the following vpc-2 atmos component
vpc-2:
metadata:
component: infra/vpc
terraform workspace in the...
what
Update atmos atlantis generate repo-config command
why
If an atmos component is derived from a base component, terraform workspace is calculated differently:
for a regular atmos component, terraform workspace is the stack name (e.g. tenant1-ue2-prod)
for a derived atmos component, terraform workspace is stack name + component name (e.g. tenant1-ue2-prod-)
For example, for the following vpc-2 atmos component
vpc-2:
metadata:
component: infra/vpc
terraform workspace in the...
rssover 3 years ago
v1.12.1
what
Update atmos atlantis generate repo-config command
why
If an atmos component is derived from a base component, terraform workspace is calculated differently:
for a regular atmos component, terraform workspace is the stack name (e.g. tenant1-ue2-prod)
for a derived atmos component, terraform workspace is stack name + component name (e.g. tenant1-ue2-prod-)
For example, for the following vpc-2 atmos component
vpc-2:
metadata:
component: infra/vpc
terraform workspace in the...
what
Update atmos atlantis generate repo-config command
why
If an atmos component is derived from a base component, terraform workspace is calculated differently:
for a regular atmos component, terraform workspace is the stack name (e.g. tenant1-ue2-prod)
for a derived atmos component, terraform workspace is stack name + component name (e.g. tenant1-ue2-prod-)
For example, for the following vpc-2 atmos component
vpc-2:
metadata:
component: infra/vpc
terraform workspace in the...
rssover 3 years ago(edited)
v1.12.2
what
Add --format=backend-config to atmos terraform generate backends command
why
Terraform supports -backend-config argument, which required the backend config files to have just the backend attributes without terraform.backend header
references
https://developer.hashicorp.com/terraform/language/settings/backends/configuration#file
test
atmos terraform generate backends...
what
Add --format=backend-config to atmos terraform generate backends command
why
Terraform supports -backend-config argument, which required the backend config files to have just the backend attributes without terraform.backend header
references
https://developer.hashicorp.com/terraform/language/settings/backends/configuration#file
test
atmos terraform generate backends...
rssover 3 years ago
v1.12.2
what
Add --format=backend-config to atmos terraform generate backends command
why
Terraform supports -backend-config argument, which required the backend config files to have just the backend attributes without terraform.backend header
references
https://developer.hashicorp.com/terraform/language/settings/backends/configuration#file
test
atmos terraform generate backends...
what
Add --format=backend-config to atmos terraform generate backends command
why
Terraform supports -backend-config argument, which required the backend config files to have just the backend attributes without terraform.backend header
references
https://developer.hashicorp.com/terraform/language/settings/backends/configuration#file
test
atmos terraform generate backends...
rssover 3 years ago(edited)
v1.3.6
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1428000452" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/812"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1428000452" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/812"...
rssover 3 years ago
v1.3.6
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1428000452" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/812"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1428000452" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/812"...
rssover 3 years ago(edited)
v1.13.1
what
Allow Helmfile component without using EKS.
why
Because atmos could be used without using EKS.
what
Allow Helmfile component without using EKS.
why
Because atmos could be used without using EKS.
rssover 3 years ago
v1.13.1
what
Allow Helmfile component without using EKS.
why
Because atmos could be used without using EKS.
what
Allow Helmfile component without using EKS.
why
Because atmos could be used without using EKS.
rssover 3 years ago(edited)
v1.13.2
what
Update docs website and atmos help commands
why
Better looking website
Improve the website color theme
Update/improve CLI/Configuration and CLI/Commands sections (https://atmos.tools/category/commands)
what
Update docs website and atmos help commands
why
Better looking website
Improve the website color theme
Update/improve CLI/Configuration and CLI/Commands sections (https://atmos.tools/category/commands)
rssover 3 years ago
v1.13.2
what
Update docs website and atmos help commands
why
Better looking website
Improve the website color theme
Update/improve CLI/Configuration and CLI/Commands sections (https://atmos.tools/category/commands)
what
Update docs website and atmos help commands
why
Better looking website
Improve the website color theme
Update/improve CLI/Configuration and CLI/Commands sections (https://atmos.tools/category/commands)
rssover 3 years ago(edited)
v1.13.3
what
Documentation website sections:
tutorials
glossary
component library
mixins
imports
why
Consolidate atmos documentation under the new docs site
what
Documentation website sections:
tutorials
glossary
component library
mixins
imports
why
Consolidate atmos documentation under the new docs site
rssover 3 years ago(edited)
Documentation Updates
Reorganize CLI commands & subcommands
Improve the introduction
Describe the AWS integrations
Reorganize CLI commands & subcommands
Improve the introduction
Describe the AWS integrations
rssover 3 years ago
rssover 3 years ago(edited)
v1.13.5
what
Standardize CLI commands formatting
Provide a general command usage page that embeds the auto-generated index
Add "Component Inheritance" section to the docs
why
It was not clear what each command should be used for without reading further down the page
Having one separate index page and an index page of subcommand led to information being sprawled across two pages, rather than having a single usage page that shows general command usage and all available subcommands
"Component...
what
Standardize CLI commands formatting
Provide a general command usage page that embeds the auto-generated index
Add "Component Inheritance" section to the docs
why
It was not clear what each command should be used for without reading further down the page
Having one separate index page and an index page of subcommand led to information being sprawled across two pages, rather than having a single usage page that shows general command usage and all available subcommands
"Component...
rssover 3 years ago
v1.13.5
what
Standardize CLI commands formatting
Provide a general command usage page that embeds the auto-generated index
Add "Component Inheritance" section to the docs
why
It was not clear what each command should be used for without reading further down the page
Having one separate index page and an index page of subcommand led to information being sprawled across two pages, rather than having a single usage page that shows general command usage and all available subcommands
"Component...
what
Standardize CLI commands formatting
Provide a general command usage page that embeds the auto-generated index
Add "Component Inheritance" section to the docs
why
It was not clear what each command should be used for without reading further down the page
Having one separate index page and an index page of subcommand led to information being sprawled across two pages, rather than having a single usage page that shows general command usage and all available subcommands
"Component...
rssover 3 years ago(edited)
v1.14.0
what
add shell completion script generation for bash, zsh, fish and powershell
users can now run atmos completion [bash|zsh|fish|powershell] and atmos will output the shell completion script for that shell
why
so users can run atmos [tab][tab] and get command auto-completion
what
add shell completion script generation for bash, zsh, fish and powershell
users can now run atmos completion [bash|zsh|fish|powershell] and atmos will output the shell completion script for that shell
why
so users can run atmos [tab][tab] and get command auto-completion
rssover 3 years ago
v1.14.0
what
add shell completion script generation for bash, zsh, fish and powershell
users can now run atmos completion [bash|zsh|fish|powershell] and atmos will output the shell completion script for that shell
why
so users can run atmos [tab][tab] and get command auto-completion
what
add shell completion script generation for bash, zsh, fish and powershell
users can now run atmos completion [bash|zsh|fish|powershell] and atmos will output the shell completion script for that shell
why
so users can run atmos [tab][tab] and get command auto-completion
rssover 3 years ago(edited)
v1.6.0
add preserve host header option @tbpoetke (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1442816690" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/124"...
add preserve host header option @tbpoetke (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1442816690" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/124"...
rssabout 3 years ago(edited)
0.146.0
what
Update stern repo
Update GitHub workflows
why
Update stern repo from https://github.com/wercker/stern (which has been deleted) to https://github.com/stern/stern
Keep GitHub workflows and READMEs up to date
what
Update stern repo
Update GitHub workflows
why
Update stern repo from https://github.com/wercker/stern (which has been deleted) to https://github.com/stern/stern
Keep GitHub workflows and READMEs up to date
rssabout 3 years ago(edited)
v1.15.0
what & why
Update atmos "deps" calculation. In some cases, when more than one different YAML stack config files imported the same import (b/c some components in both derived from the same base component), then all of those stack config files were added to the component's "deps" list (resulting in Spacelift stacks having unrelated dependency labels which would cause unnecessary stack triggering)
Document atmos completion CLI command
Add "Component-Oriented Programming" page to document...
what & why
Update atmos "deps" calculation. In some cases, when more than one different YAML stack config files imported the same import (b/c some components in both derived from the same base component), then all of those stack config files were added to the component's "deps" list (resulting in Spacelift stacks having unrelated dependency labels which would cause unnecessary stack triggering)
Document atmos completion CLI command
Add "Component-Oriented Programming" page to document...
rssabout 3 years ago(edited)
v1.4.0
Update alpine Docker tag to v3.16.3 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1446248957" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/816"...
Update alpine Docker tag to v3.16.3 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1446248957" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/816"...
rssabout 3 years ago(edited)
0.147.0
Upgrade Alpine 3.16.2 -> 3.16.3
Upgrade Debian 11.4 -> 11.5
Upgrade go 1.19.1 -> 1.19.3
Replace deprecated ::set-output with new syntax for setting GitHub action outputs
Upgrade actions to Node v16
Full release notesUpdate atmos to 1.15.0 by @cloudpossebot in...
Upgrade Alpine 3.16.2 -> 3.16.3
Upgrade Debian 11.4 -> 11.5
Upgrade go 1.19.1 -> 1.19.3
Replace deprecated ::set-output with new syntax for setting GitHub action outputs
Upgrade actions to Node v16
Full release notesUpdate atmos to 1.15.0 by @cloudpossebot in...
rssabout 3 years ago(edited)
v1.5.0
🧰 Included Tools
Update dependencies @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1465019453" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/819" data-hovercard-type="pull_request"...
🧰 Included Tools
Update dependencies @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1465019453" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/819" data-hovercard-type="pull_request"...