21 messages
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
rssabout 4 years ago(edited)
v1.5.0
Upgrade go 1.17.9 -> 1.19.0, alpine 3.15 -> 3.16 @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1360727872" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/328"...
Upgrade go 1.17.9 -> 1.19.0, alpine 3.15 -> 3.16 @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1360727872" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/328"...
rssabout 4 years ago(edited)
v1.5.0
what
Add support for custom integrations in atmos.yaml
Add Atlantis support (Atlantis is an integration)
Add atmos terraform generate varfiles and atmos atlantis generate repo-config CLI commands
why
Support Atlantis
Generate the varfiles for all components in all stacks (this is used in Atlantis repo config, and will be used to detect drifts in variables to simplify triggering Spacelift stacks)
Automatically generate Atlantis repo config file atlantis.yaml. Using the config, project and...
what
Add support for custom integrations in atmos.yaml
Add Atlantis support (Atlantis is an integration)
Add atmos terraform generate varfiles and atmos atlantis generate repo-config CLI commands
why
Support Atlantis
Generate the varfiles for all components in all stacks (this is used in Atlantis repo config, and will be used to detect drifts in variables to simplify triggering Spacelift stacks)
Automatically generate Atlantis repo config file atlantis.yaml. Using the config, project and...
rssabout 4 years ago
v1.5.0
what
Add support for custom integrations in atmos.yaml
Add Atlantis support (Atlantis is an integration)
Add atmos terraform generate varfiles and atmos atlantis generate repo-config CLI commands
why
Support Atlantis
Generate the varfiles for all components in all stacks (this is used in Atlantis repo config, and will be used to detect drifts in variables to simplify triggering Spacelift stacks)
Automatically generate Atlantis repo config file atlantis.yaml. Using the config, project and...
what
Add support for custom integrations in atmos.yaml
Add Atlantis support (Atlantis is an integration)
Add atmos terraform generate varfiles and atmos atlantis generate repo-config CLI commands
why
Support Atlantis
Generate the varfiles for all components in all stacks (this is used in Atlantis repo config, and will be used to detect drifts in variables to simplify triggering Spacelift stacks)
Automatically generate Atlantis repo config file atlantis.yaml. Using the config, project and...
rssabout 4 years ago(edited)
v1.2.4
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1330601562" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/797"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1330601562" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/797"...
rssabout 4 years ago(edited)
v1.3.0 Notable change: Preserve Dockerfile PATH
Notable change
Debian behavior is to ignore any existing value of the PATH environment variable when launching bash and set it to a predefined value. This makes it impossible to modify the PATH in the Dockerfile. Alpine's approach (taken from Arch Linux) is to append the path components to any existing PATH value, allowing users to set a preferred path, but still ensuring that all expected/required directories are included in PATH to start.
In this release, we follow Alpine's strategy under...
Notable change
Debian behavior is to ignore any existing value of the PATH environment variable when launching bash and set it to a predefined value. This makes it impossible to modify the PATH in the Dockerfile. Alpine's approach (taken from Arch Linux) is to append the path components to any existing PATH value, allowing users to set a preferred path, but still ensuring that all expected/required directories are included in PATH to start.
In this release, we follow Alpine's strategy under...
rssabout 4 years ago(edited)
v1.5.1
what
Adds a --skip-init flag which allows skipping terraform init
why
This can help speed up workflows in the case that the user knows their last command successfully ran terraform init and they do not need to run init again.
what
Adds a --skip-init flag which allows skipping terraform init
why
This can help speed up workflows in the case that the user knows their last command successfully ran terraform init and they do not need to run init again.
rssabout 4 years ago
v1.5.1
what
Adds a --skip-init flag which allows skipping terraform init
why
This can help speed up workflows in the case that the user knows their last command successfully ran terraform init and they do not need to run init again.
what
Adds a --skip-init flag which allows skipping terraform init
why
This can help speed up workflows in the case that the user knows their last command successfully ran terraform init and they do not need to run init again.
rssabout 4 years ago(edited)
v1.6.0
what
Update atmos atlantis generate repo-config command
Support native HCL output format in atmos terraform generate varfiles command
why
Do not iterate over Go maps in atmos atlantis generate repo-config command. Go iterates over maps in a non-deterministic order resulting in constant drift in the final atlantis.yaml file. Instead, get the map keys, sort them, and iterate over the sorted keys
Support native HCL output format in atmos terraform generate varfiles command - when ejecting from...
what
Update atmos atlantis generate repo-config command
Support native HCL output format in atmos terraform generate varfiles command
why
Do not iterate over Go maps in atmos atlantis generate repo-config command. Go iterates over maps in a non-deterministic order resulting in constant drift in the final atlantis.yaml file. Instead, get the map keys, sort them, and iterate over the sorted keys
Support native HCL output format in atmos terraform generate varfiles command - when ejecting from...
rssabout 4 years ago
v1.6.0
what
Update atmos atlantis generate repo-config command
Support native HCL output format in atmos terraform generate varfiles command
why
Do not iterate over Go maps in atmos atlantis generate repo-config command. Go iterates over maps in a non-deterministic order resulting in constant drift in the final atlantis.yaml file. Instead, get the map keys, sort them, and iterate over the sorted keys
Support native HCL output format in atmos terraform generate varfiles command - when ejecting from...
what
Update atmos atlantis generate repo-config command
Support native HCL output format in atmos terraform generate varfiles command
why
Do not iterate over Go maps in atmos atlantis generate repo-config command. Go iterates over maps in a non-deterministic order resulting in constant drift in the final atlantis.yaml file. Instead, get the map keys, sort them, and iterate over the sorted keys
Support native HCL output format in atmos terraform generate varfiles command - when ejecting from...
rssabout 4 years ago(edited)
v1.7.0
what
Add atmos terraform generate backends command
why
Generate terraform backend configs for all terraform components
Supported formats HCL and JSON
A GitHub Action that generates all .tfvar files and backend.tf files so that projects can be used with conventional terraform GitOps tools like atlantis, Terraform Cloud, et al.
test
# hcl is default, no need to specify it
atmos terraform generate backends --format=hcl
Writing backend config for the terraform component 'test/test-component' to...
what
Add atmos terraform generate backends command
why
Generate terraform backend configs for all terraform components
Supported formats HCL and JSON
A GitHub Action that generates all .tfvar files and backend.tf files so that projects can be used with conventional terraform GitOps tools like atlantis, Terraform Cloud, et al.
test
# hcl is default, no need to specify it
atmos terraform generate backends --format=hcl
Writing backend config for the terraform component 'test/test-component' to...
rssabout 4 years ago
v1.7.0
what
Add atmos terraform generate backends command
why
Generate terraform backend configs for all terraform components
Supported formats HCL and JSON
A GitHub Action that generates all .tfvar files and backend.tf files so that projects can be used with conventional terraform GitOps tools like atlantis, Terraform Cloud, et al.
test
# hcl is default, no need to specify it
atmos terraform generate backends --format=hcl
Writing backend config for the terraform component 'test/test-component' to...
what
Add atmos terraform generate backends command
why
Generate terraform backend configs for all terraform components
Supported formats HCL and JSON
A GitHub Action that generates all .tfvar files and backend.tf files so that projects can be used with conventional terraform GitOps tools like atlantis, Terraform Cloud, et al.
test
# hcl is default, no need to specify it
atmos terraform generate backends --format=hcl
Writing backend config for the terraform component 'test/test-component' to...
rssabout 4 years ago(edited)
v1.7.1
what
Fixes an issue where ATMOS_CLI_CONFIG_PATH points to a non directory and results in a panic.
why
This provides proper messaging and gracefully fails.
The error in question here that was getting skipped over by os.IsNotExist(err) was the following:
stat /usr/local/etc/atmos/atmos.yaml/atmos.yaml: not a directory
what
Fixes an issue where ATMOS_CLI_CONFIG_PATH points to a non directory and results in a panic.
why
This provides proper messaging and gracefully fails.
The error in question here that was getting skipped over by os.IsNotExist(err) was the following:
stat /usr/local/etc/atmos/atmos.yaml/atmos.yaml: not a directory
rssabout 4 years ago(edited)
v1.5.0
Allow to set listener tags @welderpb (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1372764886" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/122"...
Allow to set listener tags @welderpb (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1372764886" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/122"...
rssabout 4 years ago(edited)
v1.8.0
what
Remove the default hardcoded CLI config
Update TF workspace calculation for Spacelift stacks
why
Make atmos.yaml CLI config always required. Remove the default hardcoded CLI config b/c it had some default values which are not applicable for all use cases. Instead, throw error if atmos.yaml is not found
export ATMOS_LOGS_VERBOSE=true
atmos describe component test/test-component-override -s tenant1-ue2-dev
Found ENV var ATMOS_LOGS_VERBOSE=true
Searching, processing and merging atmos CLI...
what
Remove the default hardcoded CLI config
Update TF workspace calculation for Spacelift stacks
why
Make atmos.yaml CLI config always required. Remove the default hardcoded CLI config b/c it had some default values which are not applicable for all use cases. Instead, throw error if atmos.yaml is not found
export ATMOS_LOGS_VERBOSE=true
atmos describe component test/test-component-override -s tenant1-ue2-dev
Found ENV var ATMOS_LOGS_VERBOSE=true
Searching, processing and merging atmos CLI...
rssabout 4 years ago(edited)
v1.3.1 See also "notable change" in v1.3.0
Update debian Docker tag to v11.5 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1370767376" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/803"...
Update debian Docker tag to v11.5 @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1370767376" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/803"...
rssabout 4 years ago(edited)
v2.0.1
🚀 Enhancements
Updating sg egress to use input variable @joshmello (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1293184479" data-permission-text="Title is private"...
🚀 Enhancements
Updating sg egress to use input variable @joshmello (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1293184479" data-permission-text="Title is private"...
rssabout 4 years ago(edited)
v1.8.1
what
Use namespace context variable in the code that is used to return remote-state for a component in a stack
why
For stacks config using multiple Orgs, we use namespace in stack names, and need to be able to find the remote state of the components provisioned in these stack
what
Use namespace context variable in the code that is used to return remote-state for a component in a stack
why
For stacks config using multiple Orgs, we use namespace in stack names, and need to be able to find the remote state of the components provisioned in these stack
rssabout 4 years ago
v1.8.1
what
Use namespace context variable in the code that is used to return remote-state for a component in a stack
why
For stacks config using multiple Orgs, we use namespace in stack names, and need to be able to find the remote state of the components provisioned in these stack
what
Use namespace context variable in the code that is used to return remote-state for a component in a stack
why
For stacks config using multiple Orgs, we use namespace in stack names, and need to be able to find the remote state of the components provisioned in these stack
rssabout 4 years ago(edited)
v1.6.0
Update pre-commit tools @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1383359443" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/329" data-hovercard-type="pull_request"...
Update pre-commit tools @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1383359443" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/329" data-hovercard-type="pull_request"...
rssabout 4 years ago(edited)
v1.8.2
what
Fix atlantis projects generation
why
apply_requirements should be under project, not under autoplan
references
https://www.runatlantis.io/docs/repo-level-atlantis-yaml.html
what
Fix atlantis projects generation
why
apply_requirements should be under project, not under autoplan
references
https://www.runatlantis.io/docs/repo-level-atlantis-yaml.html
rssabout 4 years ago(edited)
v1.3.2 See also "notable change" in v1.3.0 Latest
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1384465718" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/804"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1384465718" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/804"...