Skip to content

Latest commit

 

History

History
50 lines (37 loc) · 2.26 KB

kp_builder_patch.md

File metadata and controls

50 lines (37 loc) · 2.26 KB

kp builder patch

Patch an existing builder configuration

Synopsis

Patch an existing builder configuration by providing command line arguments.

A buildpack order must be provided with either the path to an order yaml or via the --buildpack flag. Multiple buildpacks provided via the --buildpack flag will be added to the same order group.

The namespace defaults to the kubernetes current-context namespace.

kp builder patch <name> [flags]

Examples

kp builder patch my-builder --order /path/to/order.yaml --stack tiny --store my-store
kp builder patch my-builder --order /path/to/order.yaml
kp builder patch my-builder --buildpack my-buildpack-id --buildpack [email protected]

Options

  -b, --buildpack strings        buildpack id and optional version in the form of either '<buildpack>@<version>' or '<buildpack>'
                                   repeat for each buildpack in order, or supply once with comma-separated list
      --dry-run                  perform validation with no side-effects; no objects are sent to the server.
                                   The --dry-run flag can be used in combination with the --output flag to
                                   view the Kubernetes resource(s) without sending anything to the server.
  -h, --help                     help for patch
  -n, --namespace string         kubernetes namespace
  -o, --order string             path to buildpack order yaml
      --output string            print Kubernetes resources in the specified format; supported formats are: yaml, json.
                                   The output can be used with the "kubectl apply -f" command. To allow this, the command
                                   updates are redirected to stderr and only the Kubernetes resource(s) are written to stdout.
                                   The APIVersion of the outputted resources will always be the latest APIVersion known to kp (currently: v1alpha2).
      --service-account string   service account name to use
  -s, --stack string             stack resource to use
      --store string             buildpack store to use
  -t, --tag string               registry location where the builder will be created

SEE ALSO