chore: new googleCloudBuildRepoV2 field to configure a remote dependency #9293
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.
Related: #9236
Description
requires[].googleCloudBuildRepoV2
config key to allow a remote dependency configuration using Google Cloud Build Repositories V2oauth2
format. Now the package defines the struct it accepts to download/sync a repo instead of using thelatest.GitInfo
from the yaml schema, leaving only the necessary fields it needsremote origin
URL before triggeringgit fetch
andgit reset
. This to handle the case when we useoauth2
, the read token can expire, so we need to use the new one fetched from CBrequires[].googleCloudBuildRepoV2
andrequires[].git
, the generated folder name will be the same for both due to they use the same inputs to generate the hash (repo + ref). This shouldn't be a problem due to is the same source, and what will change is theremote origin
URL to use, or not, theoauth2
formatskaffold render
to check that the remote dependency was fetched correctly