Clarify buildpack builder defaults and overrides#462
Open
psanghvi17 wants to merge 1 commit intomainfrom
Open
Conversation
Replace Paketo-only wording with Cloud Native Buildpacks (CNB) terminology and clarify that Epinio uses a Paketo jammy full stack builder by default. Document that any CNB-compatible builder (including non-Paketo or custom builders) can be used by configuring the cluster default or passing --builder-image / staging.builder per push. Update staging scripts, manifests, supported-apps, advanced explanation, CLI help text, and the custom-builder tutorial to explain the fallback behavior and how Epinio selects staging scripts based on the builder image.
❌ Deploy Preview for epinio-docs-staging failed.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replace Paketo-only wording with Cloud Native Buildpacks (CNB) terminology and clarify that Epinio uses a Paketo jammy full stack builder by default. Document that any CNB-compatible builder (including non-Paketo or custom builders) can be used by configuring the cluster default or passing --builder-image / staging.builder per push. Update staging scripts, manifests, supported-apps, advanced explanation, CLI help text, and the custom-builder tutorial to explain the fallback behavior and how Epinio selects staging scripts based on the builder image.