Updated Agent Scaler version to 1.7.0 #1236
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change introduces a fix to AWS Lambda functions being migrated from the go 1.x runtime to the new Custom Runtime on Amazon Linux 2, see this post.
The changes to the Agent Scaler can be found in buildkite/buildkite-agent-scaler#108 to support this new Elastic Stack version.
Fixes #1203.
Note: Customers upgrading existing stacks may not be able to upgrade to the new version, there are more details in the following comments: #1172 (comment), #1172 (comment)
The current method of solving this issue is to run this command via the AWS CLI:
aws cloudformation update-stack