Skip to content

Commit 8a73fd3

Browse files
lluunnk8s-ci-robot
authored andcommitted
add doc on new package (kubeflow#911)
1 parent f99daf6 commit 8a73fd3

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

docs_dev/ksonnet_packages.md

+9-2
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,6 @@ this way changes to your .libsonnet files will automaticaly be reflected in your
7474

7575
If you make changes to prototypes you need to regenerate the prototype. You can just delete the `.jsonnet`
7676
file in your app's component directory and then regenerate the component using `ks generate`.
77-
If you use the same name you will preserve the values of any parameters you have set.
78-
ksonnet will print a warning but it works; e.g.
7977

8078
```
8179
rm -rf ${APP_DIR}/components/kubeflow-core.jsonnet
@@ -84,6 +82,15 @@ INFO Writing component at 'components/kubeflow-core'
8482
ERROR Component parameters for 'kubeflow-core' already exists
8583
```
8684

85+
#### ERROR Component parameters for 'kubeflow-core' already exists
86+
If you use the same component name you will preserve the values of any parameters you have set.
87+
ksonnet will print a warning but it works.
88+
89+
However, the parameters for the component is not changed. So if you added new
90+
@optionalParam, it will not be set in the `component/params.libsonnet` and you
91+
will see errors like `RUNTIME ERROR: Field does not exist: NEW_OPTIONAL_PARAM`.
92+
In this case, use a new component name.
93+
8794
### New Packages
8895

8996
If you are dealing with a new package you need to modify `app.yaml` in your ksonnet application

0 commit comments

Comments
 (0)