migrate to LOCALSTACK_AUTH_TOKEN #11767
Merged
Conversation
This file contains hidden or 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
f839e1d to
9acd91b
Compare
9acd91b to
e59d58b
Compare
zaingz
pushed a commit
that referenced
this pull request
Nov 11, 2024
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.
Motivation
With the upcoming release of LocalStack v4, we will push the deprecation of
LOCALSTACK_API_KEYin favor ofLOCALSTACK_AUTH_TOKEN.This PR prepares this deprecation by migrating all usages of the API key in favor of the auth token.
This change does not introduce any deprecation message yet.
Changes
LOCALSTACK_AUTH_TOKENinstead ofLOCALSTACK_API_KEYwherever possible.LOCALSTACK_API_KEYin case no credentials are set./cc @Pive01 @SimonWallner