Mark GCP Buildpacks builder as trusted in the examples #6284
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.
Fixed #5971
Description
Mark our examples using the GCP Buildpacks builder (
gcr.io/buildpacks/builder:v1
) as a trusted builder. This setting causes the pack library to use the lifecycle that is in the image instead of trying to download and run the lifecycle-as-an-image.(I'm unsure about retaining the digest in the buildpacks builder in the absence of tooling to automatically monitor and update digests, but left it in.)
This setting puts the user in charge and is simpler than having Skaffold maintain a list of trusted builders, or to see if it was possible to reuse the CNB project's method for trusted images.