Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.6.2
->v1.7.0
Release Notes
seek-jobs/gantry-buildkite-plugin
v1.7.0
Compare Source
The upgrade path for this release has been tested from 1.4.0+ due to being unable to deploy older versions due to Lambda changing which versions of Nodejs are supported. If you're using a version of Gantry prior to 1.4.0 and encounter issues, please consider upgrading to 1.4.0 and then to 1.7.0.
Links
What’s Changed
🐛 Bug Fixes
region
as attribute as well as DD tag (#1673) @bernosNotes
🧱 list-resources can include potential orphaned AWS resources
The previous behaviour of list-resources only included resources that appear to be intact and in working order (as far as Gantry can tell). This includes Gantry service, environment, or cloudformationStack. However, sometimes there are AWS resources left behind from failed first deployments, manual deletions, etc. Now, if you include the --include-incomplete flag when running list-resources, it will include a second list of AWS resources that might not be owned by a service or environment, but look like they should be. Please consider this list a list of possibly orphaned resources, and confirm if a service or environment exists that they belong to before taking any action on them.
👶 Better recovery from failed initial deploy
Gantry will now allow all resource types to overcome an initially-failed ROLLBACK_COMPLETE stack status, by implementing a cleanup action into stack deployments.
👂 Prevent listener mixup after bad apply
An apply that failed could previously get Gantry into a state where subsequent deployments could not be carried out. This has been fixed.
🖼️ Use public ECR galleries
Gantry will now use the public ECR gallery for the X-Ray and OpenTelemetry sidecars. Thanks Brendan and @Jade Montagu !
🐛 Bug Fixes
Add missing region attribute to Datadog (Thanks Brendan!)
IAM Permission Changes
If you are using least-privilege roles, you will need to add the following statement to your build agents when upgrading to gantry v1.7.0:
Configuration
📅 Schedule: "after 3:00 am and before 6:00 am every weekday" in timezone Australia/Melbourne.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.