Ensure WCP_PROJECT_ENVIRONMENT_API_KEY Doesn't Run PAT Auth
#2674
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.
Changes
Before this PR, even in the presence of the
WCP_PROJECT_ENVIRONMENT_API_KEYenvironment variable, the authentication via user's PAT (obtained when logging in viawebiny logincommand) would still be performed.This is not needed. When an API key is present, the auth should be completely done using it. This PR ensures that is the case.
How Has This Been Tested?
Manual.
Documentation
Changelog.