mirror of
https://github.com/kubernetes-sigs/kustomize.git
synced 2026-06-11 17:12:51 +00:00
rename run-fns to run
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
## run-fns
|
||||
## run
|
||||
|
||||
[Alpha] Reoncile config functions to Resources.
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
|
||||
[Alpha] Reconcile config functions to Resources.
|
||||
|
||||
run-fns sequentially invokes all config functions in the directly, providing Resources
|
||||
run sequentially invokes all config functions in the directly, providing Resources
|
||||
in the directory as input to the first function, and writing the output of the last
|
||||
function back to the directory.
|
||||
|
||||
@@ -23,7 +23,7 @@ order they appear in the file).
|
||||
#### Config Functions:
|
||||
|
||||
Config functions are specified as Kubernetes types containing a metadata.configFn.container.image
|
||||
field. This fields tells run-fns how to invoke the container.
|
||||
field. This fields tells run how to invoke the container.
|
||||
|
||||
Example config function:
|
||||
|
||||
@@ -40,7 +40,7 @@ order they appear in the file).
|
||||
spec:
|
||||
configField: configValue
|
||||
|
||||
In the preceding example, 'kustomize config run-fns example/' would identify the function by
|
||||
In the preceding example, 'kustomize config run example/' would identify the function by
|
||||
the metadata.configFn field. It would then write all Resources in the directory to
|
||||
a container stdin (running the gcr.io/example/examplefunction:v1.0.1 image). It
|
||||
would then writer the container stdout back to example/, replacing the directory
|
||||
@@ -50,4 +50,4 @@ order they appear in the file).
|
||||
|
||||
### Examples
|
||||
|
||||
kustomize config run-fns example/
|
||||
kustomize config run example/
|
||||
|
||||
Reference in New Issue
Block a user