#releases (2023-04)
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
2023-04-02
arm64 support for Debian and RPM With this release, we begin packaging arm64 versions of our Debian and RPM packages, where such binaries are available. Some projects do not publish arm64 binaries and with one exception (vert) we have not invested in building them, so those packages are missing. Those packages are marked with a * in the targets document. We also formally indicate our preference for Debian over…
v1.15.1 Bug Fixes Make package/Makefile safe for /bin/sh @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1651168126” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/build-harness/issues/343“…
2023-04-03
v2.1.0 Enhancements Install stubs for tools missing arm64 support @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1652842728” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/841“…
2023-04-04
v2.0.0 Breaking changes, Apple M1 support Enhancements Initial support for ARM @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1626510186” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/837” data-hovercard-type=”pull_request”…
2023-04-05
v2.1.1 Build/Release Maintenance Publish “latest” image to Docker hub @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1655006210” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/842“…
2023-04-07
v1.32.5 what && why Add docs for the new Atmos GitHub Actions references https://github.com/cloudposse/github-action-atmos-affected-stacks https://github.com/cloudposse/github-action-atmos-component-updater
2023-04-08
v1.33.0 what Update Atmos logs Add logs.file and logs.level to atmos.yaml Update docs https://atmos.tools/cli/configuration why Allow specifying a file for Atmos to write logs to Allow specifying a log level to control the amount of Atmos logging Logs Atmos logs are configured in the logs section: logs: file: “/dev/stdout” # Supported log levels: Trace, Debug, Info, Warning, Off (Off is the default and is used if logs.level is not…
2023-04-11
v1.16.0 chore: deprecate glide in go targets @dudymas (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1657746800” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/build-harness/issues/345“…
2023-04-12
v0.81.2 Update branding colors @osterman (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1665337893” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/docs/issues/580” data-hovercard-type=”pull_request”…
2023-04-13
v0.81.3 Enhancements Move CSS for Hero Container to Theme @osterman (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1666523213” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/docs/issues/581“…
v1.17.0 Support release branches and default branch named “main” @Nuru (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1665761698” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/build-harness/issues/346“…
v1.33.2 what Rename atmos describe dependants to atmos describe dependents Add alias to allow atmos describe dependants why There are two acceptable ways to spell dependent depending (no pun intended) on whether you are speaking American English (dependent) or British English (dependant)
v1.33.2 what Rename atmos describe dependants to atmos describe dependents Add alias to allow atmos describe dependants why There are two acceptable ways to spell dependent depending (no pun intended) on whether you are speaking American English (dependent) or British English (dependant)
2023-04-14
v1.34.0 what Update env stack config section Allow using null to unset the ENV var why If it’s set to null, it will not be set as ENV var in the executing process (will be just skipped) Setting it to null will override all other values set in the stack configs for the component This is useful if an ENV var is set globally in top-level stacks for the entire configuration, but needs to be unset for some specific components test Set TEST_ENV_VAR4 to some value components: terraform:…
2023-04-17
v2.1.2 Included Tools Update dependency cryptography to v40.0.2 @renovate (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1668633201” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/844“…
2023-04-21
2023-04-24
v2.1.3 Included Tools Update AWS CLI packages @renovate (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1679362514” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/845“…
2023-04-25
v1.34.1 what Add ExecuteDescribeStacks function to pkg package and wrap the same function from the internal package Add tests why We need to use the ExecuteDescribeStacks in the terraform utils provider, but all code in the internal package is not visible to the calling code. internal package is used to reduce the public API surface. Packages within an internal/directory are therefore said to be internal packages references <a href=”https://go.dev/doc/go1.4#internalpackages“…
2023-04-27
v1.34.2 what Add workspace to the outputs of atmos describe stacks command why We often need to know the terraform workspace for each component (taking into account that Terraform workspaces can be overridden per component, so they are not always the same as the stack names) test tenant1-ue2-dev: components: terraform:
top-level-component1:
workspace: tenant1-ue2-dev
test/test-component-override-3:
workspace: test-component-override-3-workspace
v1.34.2 what Add workspace to the outputs of atmos describe stacks command why We often need to know the terraform workspace for each component (taking into account that Terraform workspaces can be overridden per component, so they are not always the same as the stack names) test tenant1-ue2-dev: components: terraform:
top-level-component1:
workspace: tenant1-ue2-dev
test/test-component-override-3:
workspace: test-component-override-3-workspace
2023-04-29
v2.1.4 Included Tools Update AWS CLI packages @renovate (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1689267920” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/846“…