...
When you make changes in pico configurations , using topo, these are automatically validated before they are copied to the active registry.
If the command and its arguments can be parsed but fails fail the validation, you can update the configuration or use a reset command to undo the changes. An error message will appear if the validation fails. You can disable the validation by using the option --no-activation. Changes performed by the mzsh topo will then remain in the master registry until you submit a separate topo activate command.
...
Use topo env to display or set environment variables that are used my by the mzsh command. These variables are written to the script file MZ_HOME/bin/mzsh. .
The variables, MZ_PLATFORM, MZ_CONTAINER and MZ_CONTAINER_TYPE, are handled differently than the rest. To update the value in the script file you use the parameters starting with --update-<value> as per the below table. To update the value in the script file and use the value immediately, you need to combine the --update-<value> parameter with the -e parameter.
Option | Description |
|---|---|
[-e, --effective] | Use this option to read the environment parameters in runtime, i e the "effective values" after accounting for overrides. The default behaviour is to read the values as they are defineds in the mzsh script file, not accounting for the possibility to override these values with environment variables. |
[--update-java-home <value>] | Use this option to update the value of JAVA_HOME |
[--update-mz-container <value>] | Use this option to update the value of MZ_CONTAINER. |
[--update-mz-home <value> ] | Use this option to update the value of MZ_HOME. |
[--update-mz-platform <value> ] | Use this option to update the mzsh value of MZ_PLATFORM. |
...