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.8.2
->v2.0.0
Release Notes
seek-jobs/gantry-buildkite-plugin
v2.0.0
Compare Source
Links
What’s Changed
🚀 Features
🐛 Bug Fixes
Notes
👯♀️ Environment and service version matching
This is a breaking change. No action is required to upgrade, but upgrade behaviour will be different as of this version.
Environments and services no longer need to match on minor and patch versions, only major. Now, all 2.x environments and services should work together without needing to upgrade your environment every time a patch version of Gantry is released. Backwards-incompatible changes will still result in a major version bump, but these should be infrequent. Read more about our version skew policy in the Gantry docs.
👔 Auth changes
This is a breaking change. Service YAML files with these fields will no longer deploy.
Gantry and the auth sidecar no longer support OpenID and Candidate auth support. The Auth0 hirers default JWKS has been changed to .com instead of .com.au in preparation to support marketplace unification. Layer 7 JWKS is now unsupported by default, but this can still be configured manually by adding to the serviceJwksUrl field in your service YAML (although removing it is a better idea).
Thanks, Online Identity, but in particular @AliBazzi and @pierreloseek!
😵💫 EC2 deployments
This release introduces support for using EC2s in place of ECS. Using EC2s requires changes to your service and environment. Please see the Gantry docs for more details on how to use this feature.
Thanks, @huynguyent and @adbrowne!
🌜Custom environment alarm descriptions
The description for rejected connection and 5XX alarms can now be customised. Please see the 5XX and rejected connection fields to implement these.
Thanks @hananabud!
🏎 Auth sidecar improvements
The idle connection property of the auth sidecar is now configurable. Adjusting this property can result in fewer errors due to exhausting all available connections.
The auth sidecar now uses the same ulimit value as your service.
Thanks for these improvements, @weixu365!
🌡 More fields for customising health checks
The following fields are now exposed in a service YAML to customise how your service’s health checks should be carried out:
Please see the linked documentation for how to use these fields. Thanks, @weixu365!
👂 ALB listener priority changes
Previously when creating a new Gantry service in an existing environment with a routing.hosts entry that matches traffic already going to the environment, the new service may receive traffic before any tasks have been created to handle said traffic if the ALB listener rule for the new service gets created with a higher priority than the rule for the existing service that was handling that traffic. This has been fixed.
Thanks, @david-poirier!
💥 Improved AWS calls
Gantry has condensed some AWS calls to reduce the number of times certain operations will call AWS and increased the number of retries on all AWS calls to make it more resilient to throttling issues.
🥅 Bug Fixes
v1.8.3
Compare Source
Links
🐛 Bug Fixes
This release fixes an issue in the Open Telemetry sidecar that resulted in it crashing on startup.
It also fixes a segmentation fault from checking image scanning results when running
gantry build
.Configuration
📅 Schedule: Branch creation - "after 3:00 am and before 6:00 am every weekday" in timezone Australia/Melbourne, Automerge - At any time (no schedule defined).
🚦 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 Mend Renovate. View repository job log here.