Skip to content

v1.3.0

Choose a tag to compare

@cloudposse-releaser cloudposse-releaser released this 28 Aug 16:03
· 12 commits to refs/heads/main since this release

🚀 Enhancements

feature: add `process-templates` input @korenyoni (#58) ## what
  • Add process-templates input as the value of the --process-templates flag to pass to atmos describe component.
  • Add appropriate test cases.

why

  • Some template functions such as atmos.Component require authentication to remote backends. We should allow disabling this.

references

> Run cloudposse/github-action-atmos-get-setting@v1
template: all-atmos-sections:163:26: executing "all-atmos-sections" at <atmos.Component>: error calling Component: exit status 1

Error: error configuring S3 Backend: IAM Role (arn:aws:iam::xxxxxxxxxxxx:role/xxxx-core-gbl-root-tfstate) cannot be assumed.

There are a number of possible causes of this - the most common are:
  * The credentials used in order to assume the role are invalid
  * The credentials do not have appropriate permission to assume the role
  * The role ARN is not valid

Error: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

I've kept the default value of process-templates as true in order to ensure backwards compatibility.

🐛 Bug Fixes

feature: add `process-templates` input @korenyoni (#58) ## what
  • Add process-templates input as the value of the --process-templates flag to pass to atmos describe component.
  • Add appropriate test cases.

why

  • Some template functions such as atmos.Component require authentication to remote backends. We should allow disabling this.

references

> Run cloudposse/github-action-atmos-get-setting@v1
template: all-atmos-sections:163:26: executing "all-atmos-sections" at <atmos.Component>: error calling Component: exit status 1

Error: error configuring S3 Backend: IAM Role (arn:aws:iam::xxxxxxxxxxxx:role/xxxx-core-gbl-root-tfstate) cannot be assumed.

There are a number of possible causes of this - the most common are:
  * The credentials used in order to assume the role are invalid
  * The credentials do not have appropriate permission to assume the role
  * The role ARN is not valid

Error: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

I've kept the default value of process-templates as true in order to ensure backwards compatibility.

🤖 Automatic Updates

Update release workflow @osterman (#56) ## what - Update workflow (`.github/workflows/release.yaml`) to have permissions commenting PR

why

  • Add comments to PRs when it's changes are released