[DRAFT] [WIP] Use existing authToken from user machine #172
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
mkenchugonde
requested review from
bwieger-atlassian-com,
sdzh-atlassian,
cabella-dot and
marcomura
as code owners
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.
Customer Need:
We are planning this extension inside RDE which already has Bitbucket authToken. We are planning to feed the BB authToken directly to the atlascode extension without needing to go through the authorization flow and auth dance.
The token refresh will be handled externally so we need to avoid token refresh as well.
TBD:
Right now, the authToken is passed as an env variable. I intend to change this implementation to be more robust as the auth token will change.