fix: honor builder configured in func.yaml - #4033
Conversation
The generated GitHub Actions workflow always determined FUNC_BUILDER from the runtime, silently ignoring any builder configured in func.yaml. This made it impossible for library consumers to force a specific builder without patching the generated YAML after the fact. f.Build.Builder is now threaded through the workflow generator. When set, it takes precedence over the runtime default. Runtime validation still runs regardless, so unsupported runtimes are rejected even when an explicit builder is provided. Explicit builder values are also validated against the known set.
|
Hi @pmeida. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pmeida The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Changes
func config ciignoring the builder set infunc.yaml.FUNC_BUILDERin the generated workflow now reflectsbuild.builderwhen configured/kind bug
Fixes #4031
Release Note
Docs