#releases (2022-08)
Announce New Releases for Cloud Posse GitHub Projects
Archive: https://archive.sweetops.com/releases/
2022-08-01
v1.2.3 Included Tools Update AWS CLI packages @renovate (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1299518463” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/796“…
2022-08-10
v0.25.0 include protocol_version for the default target group @azarudeena (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1334456360” data-permission-text=”Title is private”…
2022-08-15
v0.25.1 Enhancements Use context tags @nitrocode (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1335019067” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/terraform-aws-alb-ingress/issues/65“…
2022-08-16
v1.4.0 Added github action docs @goruha (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1339117194” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/build-harness/issues/327” data-hovercard-type=”pull_request”…
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“…
2022-08-20
v1.4.26 what Update versions Fix handling of partial stacks definitions Improve error handling Add an example of partial stacks definition why Update Go, Docker, Terraform to the latest version to keep up to date When searching for the specified component in the specified stack (e.g. atmos describe component -s ), if any of the stack config files throws error (which also means that we can’t find the component in that stack), print the error to the console and continue searching for the component in…
v1.4.26 what Update versions Fix handling of partial stacks definitions Improve error handling Add an example of partial stacks definition why Update Go, Docker, Terraform to the latest version to keep up to date When searching for the specified component in the specified stack (e.g. atmos describe component -s ), if any of the stack config files throws error (which also means that we can’t find the component in that stack), print the error to the console and continue searching for the component in…
2022-08-24
v1.4.27 what Update atmos vendor pull why Allow using absolute and relative file paths in component.yaml when vendoring mixins. This will allow having mixins in a local folder (and not in a private GitHub repo for which you’ll have to use a GitHub token or other means to authenticate) # mixins override files from ‘source’ with the same ‘filename’ (e.g. ‘context.tf’ will override ‘context.tf’ from the ‘source’) # mixins are processed in the order they are declared in the list mixins: #…
v1.4.27 what Update atmos vendor pull why Allow using absolute and relative file paths in component.yaml when vendoring mixins. This will allow having mixins in a local folder (and not in a private GitHub repo for which you’ll have to use a GitHub token or other means to authenticate) # mixins override files from ‘source’ with the same ‘filename’ (e.g. ‘context.tf’ will override ‘context.tf’ from the ‘source’) # mixins are processed in the order they are declared in the list mixins: #…
2022-08-30
v1.4.28 what Update atmos vendor pull why When pulling in mixins, override the destination file if it already exists Prevent the error: symlink components/terraform/mixins/context.tf components/terraform/infra/vpc-flow-logs-bucket/context.tf: file exists
Thank you @Andriy Knysh (Cloud Posse) !
I’ve just tested it with 1.4.28 and it seems to be deleting the contents of the source mixin file. Doing some more testing.
The above was happening when the existing mixin file was a symlink left over from the previous behaviour.
Once I removed that and did vendor pull with no mixin in the target, it is working OK on the 1st and subsequent attempts.
i noticed that first time after updating the code, but thought it was a fluke. The 3rd-party copy lib does some strange things instead of just copying/overriding the files. Let’s keep an eye on it and if any issues, we’ll just delete the file before copying the mixin into it
Sure I will be doing this often so I’ll let you know.
I can also make it happen by switching branches. I don’t know what is doing it exactly, but the copied mixin file is converted to a symlink. After than running vendor pull again results in an empty source file.
This is with geodesic and Docker volumes, btw.
Delete before copy sounds wise.
@Joe Niland has joined the channel
2022-08-31