revert emitter instance to use AL2022 #1449
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.
Description:
The data emitter and mocked server fails to deploy correctly with AL2023 because of certain breaking changes. Notably the deprecation of
aws ecr get-login. This require changes and testing to certain commands during remote exec. So I am reverting the instances to use AL2022. Currently there is no advantage or tech debt pilling up on using AL2022 for these instances as we plan to test AL2023 with the deployment of the ADOT collector (These changes are already made).Amazon Linux 2 offers long-term support until June 30, 2025 (ref) so there are no current security risks.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.