Support projectId + userToken as alternative to projectToken for auth
#852
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
tevanoff
reviewed
Nov 7, 2023
ghengeveld
added
release
|
🚀 PR was released in |
ghengeveld
added
the
prerelease
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Fixes AP-3383
Depends on https://github.com/chromaui/chromatic/pull/7913
This adds support for authentication via
projectIdanduserToken, as an alternative to passing aprojectToken. Currently only via the Node API (not as a flag).This uses a new mutation
createCLITokenon the public API to generate an "app token" that's compatible with the app token we'd otherwise get through the existingcreateAppTokenmutation.📦 Published PR as canary version:
7.6.1--canary.852.6771374764.0✨ Test out this PR locally via:
npm install chromatic@7.6.1--canary.852.6771374764.0 # or yarn add chromatic@7.6.1--canary.852.6771374764.0