Versioned configurations provide the option of predefined configurations of any content type (i.e. text files, binary files, etc.).
You add versioned configurations with the following command:
$ iectl publisher standalone-app app-config add \
--appname "my cool app" \
--configname "my_version_config1" \
--configdescription "displayed to the end-user during deployment" \
--hostpath "./cfg-data/" \ # volume name or relative host path with bind
--subpath "" \
--secure \ # Enabling the secure flag only stores the configuration encrypted on the Industrial Edge Management, but not on the Industrial Edge Device
--versioned \
--versionname "displayed to the end-user as selection option" \
--versiondescription "displayed to the end-user as selection option" \
--filepath /path/to/configuration/file # filepath: File that shall finally be used as input
Info
The behavior of host- and subpath are the same as for Unversioned configuration, but the filename is take from source file specified under filepath. For the example configuration above the resulting file location inside the container would then be /cfg-data/file (assuming the standard bind of "./cfg-data/:/cfg-data/").