27 messages
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
rssalmost 4 years ago(edited)
v0.152.5
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1190459518" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/779" data-hovercard-type="pull_request"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1190459518" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/779" data-hovercard-type="pull_request"...
rssalmost 4 years ago(edited)
v1.4.1
what
Add settings.spacelift.stack_name_pattern
Fix parsing YAML config and detection of stacks when the stack name (on the command line) is the same as the YAML config file name in a subfolder
why
settings.spacelift.stack_name_pattern allows overriding Spacelift stack names. Supported tokens: {namespace}, {tenant}, {environment}, {stage}, {component}
components:
terraform:
"test/test-component-override-2":
settings:
spacelift:
workspace_enabled: true
#...
what
Add settings.spacelift.stack_name_pattern
Fix parsing YAML config and detection of stacks when the stack name (on the command line) is the same as the YAML config file name in a subfolder
why
settings.spacelift.stack_name_pattern allows overriding Spacelift stack names. Supported tokens: {namespace}, {tenant}, {environment}, {stage}, {component}
components:
terraform:
"test/test-component-override-2":
settings:
spacelift:
workspace_enabled: true
#...
rssalmost 4 years ago(edited)
v1.4.2
what
Add init_run_reconfigure CLI config
Update stack_name_pattern
Disable running terraform plan and terraform workspace on abstract components
why
init_run_reconfigure CLI config allows enabling/disabling the -reconfigure argument for terraform init when running it before running other terraform commands
Don't use the default stack_name_pattern because it used {tenant} which is not available for all clients
Running terraform plan and terraform workspace on abstract components creates...
what
Add init_run_reconfigure CLI config
Update stack_name_pattern
Disable running terraform plan and terraform workspace on abstract components
why
init_run_reconfigure CLI config allows enabling/disabling the -reconfigure argument for terraform init when running it before running other terraform commands
Don't use the default stack_name_pattern because it used {tenant} which is not available for all clients
Running terraform plan and terraform workspace on abstract components creates...
rssalmost 4 years ago
v1.4.2
what
Add init_run_reconfigure CLI config
Update stack_name_pattern
Disable running terraform plan and terraform workspace on abstract components
why
init_run_reconfigure CLI config allows enabling/disabling the -reconfigure argument for terraform init when running it before running other terraform commands
Don't use the default stack_name_pattern because it used {tenant} which is not available for all clients
Running terraform plan and terraform workspace on abstract components creates...
what
Add init_run_reconfigure CLI config
Update stack_name_pattern
Disable running terraform plan and terraform workspace on abstract components
why
init_run_reconfigure CLI config allows enabling/disabling the -reconfigure argument for terraform init when running it before running other terraform commands
Don't use the default stack_name_pattern because it used {tenant} which is not available for all clients
Running terraform plan and terraform workspace on abstract components creates...
rssalmost 4 years ago(edited)
v1.0.0
Update framework, version pinning @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1197894692" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/113" data-hovercard-type="pull_request"...
Update framework, version pinning @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1197894692" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-alb/issues/113" data-hovercard-type="pull_request"...
rssalmost 4 years ago(edited)
v1.0.0
Initial release with production Semantic Versioning, part of our general strategy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. This module will evolve with breaking changes as we convert it to use our security-group and s3-log-storage modules and be compatible with the new S3 resource structure introduced in AWS...
Initial release with production Semantic Versioning, part of our general strategy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. This module will evolve with breaking changes as we convert it to use our security-group and s3-log-storage modules and be compatible with the new S3 resource structure introduced in AWS...
rssalmost 4 years ago(edited)
v1.4.3
what
Add --dry-run command-line flag to all commands and workflows
why
Helps debugging atmos commands and workflows
The --dry-run flag shows all the flow and commands without executing them and without writing files to the file system (e.g. varfiles and backend config are not written)
The --dry-run flag shows all the workflow steps without executing them
test
atmos terraform plan test/test-component-override -s=tenant1-ue2-dev --dry-run
Variables for the component...
what
Add --dry-run command-line flag to all commands and workflows
why
Helps debugging atmos commands and workflows
The --dry-run flag shows all the flow and commands without executing them and without writing files to the file system (e.g. varfiles and backend config are not written)
The --dry-run flag shows all the workflow steps without executing them
test
atmos terraform plan test/test-component-override -s=tenant1-ue2-dev --dry-run
Variables for the component...
rssalmost 4 years ago(edited)
v1.4.4
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, components-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, components-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
rssalmost 4 years ago(edited)
v1.4.4
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, component-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, component-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
rssalmost 4 years ago(edited)
v1.4.5
what
Fix detection of component dependencies for imported YAML config files
why
If a file was imported and did not contain a vars section, global or related to the component, the imported file was not included in the component dependencies (deps section), and a Spacelift label for the file was not created (if the imported file changes, Spacelift would not notice the change and would not run the stack)
Update the dependencies logic to check for these sections: backend, backend_type, env,...
what
Fix detection of component dependencies for imported YAML config files
why
If a file was imported and did not contain a vars section, global or related to the component, the imported file was not included in the component dependencies (deps section), and a Spacelift label for the file was not created (if the imported file changes, Spacelift would not notice the change and would not run the stack)
Update the dependencies logic to check for these sections: backend, backend_type, env,...
rssalmost 4 years ago(edited)
v1.4.6
what
If auto_generate_backend_file is true (we are auto-generating backend files), remove backend.tf.json when executing atmos terraform clean command
why
Useful when using different backends for the same component in different stacks
what
If auto_generate_backend_file is true (we are auto-generating backend files), remove backend.tf.json when executing atmos terraform clean command
why
Useful when using different backends for the same component in different stacks
rssalmost 4 years ago(edited)
v1.4.7
what
Take into account init_run_reconfigure CLI config and --init-run-reconfigure command-line argument when running atmos terraform init ... command
why
atmos terraform init must behave the same as all other commands that use init_run_reconfigure CLI config and --init-run-reconfigure command-line argument
what
Take into account init_run_reconfigure CLI config and --init-run-reconfigure command-line argument when running atmos terraform init ... command
why
atmos terraform init must behave the same as all other commands that use init_run_reconfigure CLI config and --init-run-reconfigure command-line argument
rssalmost 4 years ago(edited)
v1.0.0 Initial release with production Semantic Versioning
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature code.
Changes since v0.152.5:
🧰 Included Tools
Update AWS CLI packages <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/renovate/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self"...
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature code.
Changes since v0.152.5:
🧰 Included Tools
Update AWS CLI packages <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/renovate/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self"...
rssalmost 4 years ago(edited)
v0.62.3
🐛 Bug Fixes
GitHub action updates @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1205920091" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/313" data-hovercard-type="pull_request"...
🐛 Bug Fixes
GitHub action updates @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1205920091" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/313" data-hovercard-type="pull_request"...
rssalmost 4 years ago(edited)
v1.0.0 Initial release with production Semantic Versioning
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature code.
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature code.
rssalmost 4 years ago(edited)
v1.4.8
what
Add metadata.terraform_workspace_pattern
why
We already have metadata.terraform_workspace using which we can specify/override the terraform workspace for a component
metadata.terraform_workspace_pattern introduces a pattern to override a terraform workspace for a component
metadata:
# Override Terraform workspace
terraform_workspace: xxxxxxxxxxxxxxx
terraform_workspace_pattern: "{tenant}-{environment}-{stage}-{component}"
The following tokens are supported...
what
Add metadata.terraform_workspace_pattern
why
We already have metadata.terraform_workspace using which we can specify/override the terraform workspace for a component
metadata.terraform_workspace_pattern introduces a pattern to override a terraform workspace for a component
metadata:
# Override Terraform workspace
terraform_workspace: xxxxxxxxxxxxxxx
terraform_workspace_pattern: "{tenant}-{environment}-{stage}-{component}"
The following tokens are supported...
rssalmost 4 years ago(edited)
v1.4.9
what
Add atmos aws commands
Add atmos aws eks update-kubeconfig command
why
Execute aws CLI commands using atmos context (atmos.yaml CLI config and component/stack configurations)
Downloading kubeconfig from an EKS cluster using `atmos
Allow using this functionality in Terraform by implementing a new data source in the terraform-provider-utils provider (this will be added in a PR in <a...
what
Add atmos aws commands
Add atmos aws eks update-kubeconfig command
why
Execute aws CLI commands using atmos context (atmos.yaml CLI config and component/stack configurations)
Downloading kubeconfig from an EKS cluster using `atmos
Allow using this functionality in Terraform by implementing a new data source in the terraform-provider-utils provider (this will be added in a PR in <a...
rssalmost 4 years ago(edited)
v1.4.10
what
If functions that are used by Terraform providers throw errors, print errors to std.Error
why
Terraform providers only see errors that are sent to std.Error
what
If functions that are used by Terraform providers throw errors, print errors to std.Error
why
Terraform providers only see errors that are sent to std.Error
rssalmost 4 years ago(edited)
v1.4.11
what
Support dashes - in the tenant, environment and stage names
In the examples, add a new stage test-1 and add tests for components, stacks, and spacelift to test having a dash in the stage name (the file name itself being without dashes)
why
The old atmos supported it (because it was filename-based, not logical stack name based)
Some clients want to name tenants/environment/stages with dashes in the names (and some already have it, so we need to support that when converting from the old to...
what
Support dashes - in the tenant, environment and stage names
In the examples, add a new stage test-1 and add tests for components, stacks, and spacelift to test having a dash in the stage name (the file name itself being without dashes)
why
The old atmos supported it (because it was filename-based, not logical stack name based)
Some clients want to name tenants/environment/stages with dashes in the names (and some already have it, so we need to support that when converting from the old to...
rssalmost 4 years ago(edited)
v1.0.1
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1213008833" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/781"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1213008833" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/781"...
rssalmost 4 years ago(edited)
v1.4.3
what
Add --dry-run command-line flag to all commands and workflows
why
Helps debugging atmos commands and workflows
The --dry-run flag shows all the flow and commands without executing them and without writing files to the file system (e.g. varfiles and backend config are not written)
The --dry-run flag shows all the workflow steps without executing them
tests and examples
Click to expandatmos terraform plan test/test-component-override -s=tenant1-ue2-dev --dry-run
Variables for the...
what
Add --dry-run command-line flag to all commands and workflows
why
Helps debugging atmos commands and workflows
The --dry-run flag shows all the flow and commands without executing them and without writing files to the file system (e.g. varfiles and backend config are not written)
The --dry-run flag shows all the workflow steps without executing them
tests and examples
Click to expandatmos terraform plan test/test-component-override -s=tenant1-ue2-dev --dry-run
Variables for the...
rssalmost 4 years ago(edited)
v1.4.4
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, component-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
what
Add atmos describe stacks command
Allow writing the result to a file by using --file command-line flag
Allow formatting the result as YAML or JSON by using --format command-line flag
Allow filtering of the result by using the command-line flags: stack, component-types, components, sections
Available component sections: backend, backend_type, deps, env, inheritance, metadata, remote_state_backend, remote_state_backend_type, settings, vars
why
Command to show stack configs and all the...
rssalmost 4 years ago(edited)
v1.0.1
fix typo @osterman (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1216376678" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/317" data-hovercard-type="pull_request"...
fix typo @osterman (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1216376678" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/317" data-hovercard-type="pull_request"...
rssalmost 4 years ago(edited)
v1.0.2
Better handling of git "safe.directory" @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1216368382" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/316"...
Better handling of git "safe.directory" @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1216368382" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/316"...
rssalmost 4 years ago(edited)
v0.46.0
Output cloudwatch log group name @woz5999 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1217823996" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/149"...
Output cloudwatch log group name @woz5999 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1217823996" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/149"...
rssalmost 4 years ago
v1.1.0 git.io documentation update
Allow disabling CODEOWNERS automatic update, Fix Docker image build on Workflow Dispatch @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1219087998" data-permission-text="Title is private"...
Allow disabling CODEOWNERS automatic update, Fix Docker image build on Workflow Dispatch @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1219087998" data-permission-text="Title is private"...