bootstrap: Add support for Git HTTP/S authorization header #4728
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
stefanprodan
changed the title
toomaj
force-pushed
the
support-git-authorization-header
branch
2 times, most recently
from
4915fdf
to
ae7128e
Compare
Signed-off-by: toomaj <toomaj@tuta.io> Set tokenAuth to true with withBearerToken Signed-off-by: toomaj <toomaj@tuta.io> Set breaderToken if tokenAuth & withBearerToken were set Signed-off-by: toomaj <toomaj@tuta.io>
toomaj
force-pushed
the
support-git-authorization-header
branch
from
ae7128e
to
9ff9f2b
Compare
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.
This pull request introduces the capability to use Personal Access Tokens (PATs) as bearer tokens for authenticating Git operations in Oracle Visual Builder Studio (VBS). Oracle VBS requires that PATs be included in the Authorization header to secure Git operations. To facilitate this, a new flag, --with-bearer-token, has been added. When enabled, this flag treats the provided password as a bearer token, aligning with Oracle VBS's authentication requirements.
This change is crucial for developers leveraging Oracle VBS who need to integrate with Flux's automation capabilities in environments that mandate bearer token authentication. For detailed guidance on configuring PATs in Oracle VBS, please refer to the Oracle documentation: Access a Git Repository Using Token-Based Authentication