PipelineCloud allows token on creation and auto-auth if token is defined #67
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
bjornaer
added
enhancement
alexpearce
reviewed
Mar 23, 2022
alexpearce
reviewed
Mar 23, 2022
Co-authored-by: Alex Pearce <alex@mystic.ai>
alexpearce
approved these changes
Mar 23, 2022
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.
Introducing changes based on the enhancement request on issue 66
PipelineCloud now can receive a user token directly on instantiation and if it is provided either as an arg or env variable the authenticate method is immediately executed. Otherwise it must be done manually once user defined their user token