27 messages
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
rssover 3 years ago(edited)
v1.9.0
what
Add atmos components validation using JSON Schema and OPA policies
why
Validate component config (vars, settings, backend, and other sections) using JSON Schema
Check if the component config (including relations between different component variables) is correct to allow or deny component provisioning using OPA/Rego policies
Implement validation by atmos validate component command, and by adding a new section settings.validation to the component stack config to be used in other atmos...
what
Add atmos components validation using JSON Schema and OPA policies
why
Validate component config (vars, settings, backend, and other sections) using JSON Schema
Check if the component config (including relations between different component variables) is correct to allow or deny component provisioning using OPA/Rego policies
Implement validation by atmos validate component command, and by adding a new section settings.validation to the component stack config to be used in other atmos...
rssover 3 years ago
v1.9.0
what
Add atmos components validation using JSON Schema and OPA policies
why
Validate component config (vars, settings, backend, and other sections) using JSON Schema
Check if the component config (including relations between different component variables) is correct to allow or deny component provisioning using OPA/Rego policies
Implement validation by atmos validate component command, and by adding a new section settings.validation to the component stack config to be used in other atmos...
what
Add atmos components validation using JSON Schema and OPA policies
why
Validate component config (vars, settings, backend, and other sections) using JSON Schema
Check if the component config (including relations between different component variables) is correct to allow or deny component provisioning using OPA/Rego policies
Implement validation by atmos validate component command, and by adding a new section settings.validation to the component stack config to be used in other atmos...
rssover 3 years ago(edited)
v1.6.1
🐛 Bug Fixes
update github action template @mcalhoun (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1395225251" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/331"...
🐛 Bug Fixes
update github action template @mcalhoun (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1395225251" data-permission-text="Title is private" data-url="https://github.com/cloudposse/build-harness/issues/331"...
rssover 3 years ago(edited)
v1.9.1
what
Add atmos CLI config path and atmos base path parameters to the component processor to support components remote state from remote repos (Note that this does not affect atmos functionality, this is to be used in the utils provider which calls into the atmos code)
why
The component processor's code is used by the utils provider to get the component's remote state
We already supported the ATMOS_CLI_CONFIG_PATH and ATMOS_BASE_PATH ENV vars to specify the CLI config file (atmos.yaml) path...
what
Add atmos CLI config path and atmos base path parameters to the component processor to support components remote state from remote repos (Note that this does not affect atmos functionality, this is to be used in the utils provider which calls into the atmos code)
why
The component processor's code is used by the utils provider to get the component's remote state
We already supported the ATMOS_CLI_CONFIG_PATH and ATMOS_BASE_PATH ENV vars to specify the CLI config file (atmos.yaml) path...
rssover 3 years ago
v1.9.1
what
Add atmos CLI config path and atmos base path parameters to the component processor to support components remote state from remote repos (Note that this does not affect atmos functionality, this is to be used in the utils provider which calls into the atmos code)
why
The component processor's code is used by the utils provider to get the component's remote state
We already supported the ATMOS_CLI_CONFIG_PATH and ATMOS_BASE_PATH ENV vars to specify the CLI config file (atmos.yaml) path...
what
Add atmos CLI config path and atmos base path parameters to the component processor to support components remote state from remote repos (Note that this does not affect atmos functionality, this is to be used in the utils provider which calls into the atmos code)
why
The component processor's code is used by the utils provider to get the component's remote state
We already supported the ATMOS_CLI_CONFIG_PATH and ATMOS_BASE_PATH ENV vars to specify the CLI config file (atmos.yaml) path...
rssover 3 years ago(edited)
v1.3.3 Update scripts for yq v4 CLI changes
🐛 Bug Fixes
Update scripts for yq v4 CLI changes @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1401877793" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/808"...
🐛 Bug Fixes
Update scripts for yq v4 CLI changes @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1401877793" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/808"...
rssover 3 years ago(edited)
v0.49.5
Add git push proposed run test @nitrocode (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1236332426" data-permission-text="Title is private"...
Add git push proposed run test @nitrocode (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1236332426" data-permission-text="Title is private"...
rssover 3 years ago(edited)
v1.10.0
what
Fix remote state for Terraform utils provider
Remove all global vars from Go code
Implement Logs.Verbose
Update terraform commands
Refactor
why
Remove all global vars from Go code - this fixes remote state for Terraform utils provider
Terraform executes a provider data source in a separate process and calls it using RPC
But this separate process is only one per provider, so if we call the code the get the remote state of two different components, the same process will be called
In the...
what
Fix remote state for Terraform utils provider
Remove all global vars from Go code
Implement Logs.Verbose
Update terraform commands
Refactor
why
Remove all global vars from Go code - this fixes remote state for Terraform utils provider
Terraform executes a provider data source in a separate process and calls it using RPC
But this separate process is only one per provider, so if we call the code the get the remote state of two different components, the same process will be called
In the...
rssover 3 years ago
v1.10.0
what
Fix remote state for Terraform utils provider
Remove all global vars from Go code
Implement Logs.Verbose
Update terraform commands
Refactor
why
Remove all global vars from Go code - this fixes remote state for Terraform utils provider
Terraform executes a provider data source in a separate process and calls it using RPC
But this separate process is only one per provider, so if we call the code the get the remote state of two different components, the same process will be called
In the...
what
Fix remote state for Terraform utils provider
Remove all global vars from Go code
Implement Logs.Verbose
Update terraform commands
Refactor
why
Remove all global vars from Go code - this fixes remote state for Terraform utils provider
Terraform executes a provider data source in a separate process and calls it using RPC
But this separate process is only one per provider, so if we call the code the get the remote state of two different components, the same process will be called
In the...
rssover 3 years ago(edited)
v2.4.0 Warning, new feature will likely be removed
Custom Ingress rules @IkePCampbell (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1340744427" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/162"...
Custom Ingress rules @IkePCampbell (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1340744427" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/162"...
rssover 3 years ago(edited)
v2.4.0
Custom Ingress rules @IkePCampbell (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1340744427" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/162"...
Custom Ingress rules @IkePCampbell (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1340744427" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/162"...
rssover 3 years ago(edited)
v1.10.2
what
Update atmos describe stacks command
why
Output atmos stack names (logical stacks derived from the context variables) instead of stack file names
In the -s (--stack) filter, support both 1) atmos stack names (logical stacks derived from the context variables); 2) stack file names
test
atmos describe stacks --sections none --components vpc
tenant1-ue2-dev:
components:
terraform:
vpc: {}
tenant1-ue2-prod:
components:
terraform:
vpc: {}
tenant1-ue2-staging:...
what
Update atmos describe stacks command
why
Output atmos stack names (logical stacks derived from the context variables) instead of stack file names
In the -s (--stack) filter, support both 1) atmos stack names (logical stacks derived from the context variables); 2) stack file names
test
atmos describe stacks --sections none --components vpc
tenant1-ue2-dev:
components:
terraform:
vpc: {}
tenant1-ue2-prod:
components:
terraform:
vpc: {}
tenant1-ue2-staging:...
rssover 3 years ago
v1.10.2
what
Update atmos describe stacks command
why
Output atmos stack names (logical stacks derived from the context variables) instead of stack file names
In the -s (--stack) filter, support both 1) atmos stack names (logical stacks derived from the context variables); 2) stack file names
test
atmos describe stacks --sections none --components vpc
tenant1-ue2-dev:
components:
terraform:
vpc: {}
tenant1-ue2-prod:
components:
terraform:
vpc: {}
tenant1-ue2-staging:...
what
Update atmos describe stacks command
why
Output atmos stack names (logical stacks derived from the context variables) instead of stack file names
In the -s (--stack) filter, support both 1) atmos stack names (logical stacks derived from the context variables); 2) stack file names
test
atmos describe stacks --sections none --components vpc
tenant1-ue2-dev:
components:
terraform:
vpc: {}
tenant1-ue2-prod:
components:
terraform:
vpc: {}
tenant1-ue2-staging:...
rssover 3 years ago(edited)
v1.10.3
what
Update atmos.yaml initialization
why
For some atmos commands (e.g. atmos version and atmos vendor), don't process stacks b/c stacks folder might not be present (e.g. during cold-start when using atmos vendor and atmos version in CI/CD systems)
what
Update atmos.yaml initialization
why
For some atmos commands (e.g. atmos version and atmos vendor), don't process stacks b/c stacks folder might not be present (e.g. during cold-start when using atmos vendor and atmos version in CI/CD systems)
rssover 3 years ago
v1.10.3
what
Update atmos.yaml initialization
why
For some atmos commands (e.g. atmos version and atmos vendor), don't process stacks b/c stacks folder might not be present (e.g. during cold-start when using atmos vendor and atmos version in CI/CD systems)
what
Update atmos.yaml initialization
why
For some atmos commands (e.g. atmos version and atmos vendor), don't process stacks b/c stacks folder might not be present (e.g. during cold-start when using atmos vendor and atmos version in CI/CD systems)
rssover 3 years ago(edited)
v2.5.0
🐛 Bug Fixes
Better behavior during destroy @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1412275011" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/169"...
🐛 Bug Fixes
Better behavior during destroy @Nuru (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1412275011" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-eks-cluster/issues/169"...
rssover 3 years ago(edited)
v1.3.4
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1409988878" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/810"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1409988878" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/810"...
rssover 3 years ago(edited)
v0.7.2
git.io->cloudposse.tools update @dylanbannon (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1221299220" data-permission-text="Title is private"...
git.io->cloudposse.tools update @dylanbannon (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1221299220" data-permission-text="Title is private"...
rssover 3 years ago(edited)
v1.10.4
what
Parse atmos.yaml CLI config when executing atmos vendor command
Improve OPA policy evaluation and error handling
why
When executing atmos vendor pull command, we need to parse atmos.yaml and calculate the paths to stacks and components folders to write the vendored files into the correct component folder
Add timeout to OPA policy evaluation (it will show a descriptive error message instead of hanging forever if Rego policy is not correctly defined/formatted or Regex in Rego is not...
what
Parse atmos.yaml CLI config when executing atmos vendor command
Improve OPA policy evaluation and error handling
why
When executing atmos vendor pull command, we need to parse atmos.yaml and calculate the paths to stacks and components folders to write the vendored files into the correct component folder
Add timeout to OPA policy evaluation (it will show a descriptive error message instead of hanging forever if Rego policy is not correctly defined/formatted or Regex in Rego is not...
rssover 3 years ago
v1.10.4
what
Parse atmos.yaml CLI config when executing atmos vendor command
Improve OPA policy evaluation and error handling
why
When executing atmos vendor pull command, we need to parse atmos.yaml and calculate the paths to stacks and components folders to write the vendored files into the correct component folder
Add timeout to OPA policy evaluation (it will show a descriptive error message instead of hanging forever if Rego policy is not correctly defined/formatted or Regex in Rego is not...
what
Parse atmos.yaml CLI config when executing atmos vendor command
Improve OPA policy evaluation and error handling
why
When executing atmos vendor pull command, we need to parse atmos.yaml and calculate the paths to stacks and components folders to write the vendored files into the correct component folder
Add timeout to OPA policy evaluation (it will show a descriptive error message instead of hanging forever if Rego policy is not correctly defined/formatted or Regex in Rego is not...
rssover 3 years ago(edited)
v0.22.0
Support insight_selector @v3rm0n (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1415046808" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-cloudtrail/issues/59"...
Support insight_selector @v3rm0n (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1415046808" data-permission-text="Title is private" data-url="https://github.com/cloudposse/terraform-aws-cloudtrail/issues/59"...
rssover 3 years ago(edited)
v1.3.5
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1419005028" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/811"...
🧰 Included Tools
Update AWS CLI packages @renovate (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1419005028" data-permission-text="Title is private" data-url="https://github.com/cloudposse/geodesic/issues/811"...
rssover 3 years ago(edited)
v0.47.1
🚀 Enhancements
Replaced deprecated arguments policy documents @comrumino (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1421134660" data-permission-text="Title is private"...
🚀 Enhancements
Replaced deprecated arguments policy documents @comrumino (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1421134660" data-permission-text="Title is private"...
rssover 3 years ago(edited)
v0.47.2
🚀 Enhancements
Fixed potential self-escalation from iam:PassRole @comrumino (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1421249261" data-permission-text="Title is private"...
🚀 Enhancements
Fixed potential self-escalation from iam:PassRole @comrumino (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1421249261" data-permission-text="Title is private"...
rssover 3 years ago(edited)
v1.10.5
what
In atmos helmfile commands, first check if the context ENV vars are already defined. If they are not, set them in the code
why
Some users of atmos define the context ENV vars (e.g. REGION) in the caller scripts, and atmos overrides them. This fix will first check if the ENV vars are not defined by the parent process before setting them
what
In atmos helmfile commands, first check if the context ENV vars are already defined. If they are not, set them in the code
why
Some users of atmos define the context ENV vars (e.g. REGION) in the caller scripts, and atmos overrides them. This fix will first check if the ENV vars are not defined by the parent process before setting them
rssover 3 years ago(edited)
v0.50.0
Filter components by tags @nitrocode (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1422668788" data-permission-text="Title is private"...
Filter components by tags @nitrocode (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1422668788" data-permission-text="Title is private"...