Add support for using a HTTPS catalog URL for arbitrary catalogs #11
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 PR introduces logic which configures a Git
insteadOf
which injects the CI variablesACCESS_USER_<cluster_id>
(which is optional and falls back totoken
if it's not set) andACCESS_TOKEN_<cluster_id>
(which must be present) for catalog URLs that are HTTPS on Lieutenant.For example, the change will run the following
git
command for catalog URL "https://git.example.com/c-cluster-id-1234.git" for clustesrc-cluster-id-1234
:Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
in the correct changelog section:
bug
,enhancement
,documentation
,change
,breaking
,dependency
,internal