There is a command group 'az_iot_du_update_init'. This group of commands could 'utility for import manifest initialization'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_iot_du_update_init_v5'.The syntax is: az iot du update init v5 --compat
                         --step
                         --update-name
                         --update-provider
                         --update-version
                         [--description]
                         [--file]
                         [--is-deployable {false, true}]
                         [--no-validation {false, true}]
                         [--related-file]. The 1th example of the child command would be to use it to 'initialize a minimum content import manifest  inline json optimized for  bash', the syntax is: az iot du update init v5 --update-provider Microsoft --update-name myAptUpdate --update-version 1.0.0 --description "My minimum update" --compat manufacturer=Contoso model=Vacuum --step handler=microsoft/apt:1 properties='{"installedCriteria": "1.0"}' --file path=/my/apt/manifest/file. The 2th example of the child command would be to use it to 'initialize a minimum content import manifest  inline json optimized for  powershell', the syntax is: az iot du update init v5 --update-provider Microsoft --update-name myAptUpdate --update-version 1.0.0 --description "My minimum update" --compat manufacturer=Contoso model=Vacuum --step handler=microsoft/apt:1 properties='{\"installedCriteria\": \"1.0\"}' --file path=/my/apt/manifest/file. The 3th example of the child command would be to use it to 'initialize a minimum content import manifest  inline json optimized for  cmd', the syntax is: az iot du update init v5 --update-provider Microsoft --update-name myAptUpdate --update-version 1.0.0 --description "My minimum update" --compat manufacturer=Contoso model=Vacuum --step handler=microsoft/apt:1 properties="{\"installedCriteria\": \"1.0\"}" --file path=/my/apt/manifest/file. The 4th example of the child command would be to use it to 'initialize a minimum content import manifest  use file input for json', the syntax is: az iot du update init v5 --update-provider Microsoft --update-name myAptUpdate --update-version 1.0.0 --description "My minimum update" --compat manufacturer=Contoso model=Vacuum --step handler=microsoft/apt:1 properties="@/path/to/file" --file path=/my/apt/manifest/file. The 5th example of the child command would be to use it to 'initialize a non deployable leaf update to be referenced in a bundled update  inline json optimized for  bash', the syntax is: az iot du update init v5 --update-provider Microsoft --update-name mySwUpdate --update-version 1.1.0 --compat manufacturer=Contoso model=Microphone --step handler=microsoft/swupdate:1 description="Deploy Update" properties='{"installedCriteria": "1.0"}' --file path=/my/update/image/file1 --file path=/my/update/image/file2 --is-deployable false. The 6th example of the child command would be to use it to 'initialize a bundled update referencing a leaf update as well as defining independent steps  example optimized for  bash  using command continuation to delineate import manifest segments', the syntax is: az iot du update init v5 \
--update-provider Microsoft --update-name myBundled --update-version 2.0 \
--compat manufacturer=Contoso model=SpaceStation \
--step handler=microsoft/script:1 properties='{"arguments": "--pre"}' description="Pre-install script" \
--file path=/my/update/scripts/preinstall.sh downloadHandler=microsoft/delta:1 \
--related-file path=/my/update/scripts/related_preinstall.json properties='{"microsoft.sourceFileHashAlgorithm": "sha256"}' \
--step updateId.provider=Microsoft updateId.name=SwUpdate updateId.version=1.1 \
--step handler=microsoft/script:1 properties='{"arguments": "--post"}' description="Post-install script" \
--file path=/my/update/scripts/postinstall.sh. The parameter '--compat' is required. It is used to space-separated key=value pairs corresponding to properties of a device this update is compatible with. typically used for defining properties such as manufacturer and model. --compat can be used 1 or more times.. The parameter '--step' is required. It is used to space-separated key=value pairs corresponding to 'instructions.steps' element properties. the client will determine if a step is an inline or reference step based on the provided key value pairs. if either inline or reference step can be satisfied, the reference step will be prioritized. usage of --file will be associated with the nearest inline --step entry, deriving the value for 'files'. the following reference step keys are supported: `updateid.provider`, `updateid.name`, `updateid.version` and `description`. the following inline step keys are supported: `handler` (ex: 'microsoft/script:1' or 'microsoft/swupdate:1' or 'microsoft/apt:1'), `properties` (in-line json object the agent will pass to the handler), and `description`. --step can be used 1 or more times.. The parameter '--update-name' is required. It is used to the update name as a component of updateid.. The parameter '--update-provider' is required. It is used to the update provider as a component of updateid.. The parameter '--update-version' is required. It is used to the update version as a component of updateid.. The parameter '--description' is optional. description for the import manifest.. The parameter '--file' is optional. space-separated key=value pairs corresponding to 'files' element properties. a --file entry can include the closest --related-file entries if provided. the following keys are supported: `path` [required] local file path to update file, `downloadhandler` (ex: 'microsoft/delta:1') handler for utilizing related files to download payload file, `properties` (in-line json object the agent will pass to the handler). --file can be used 1 or more times.. The parameter '--is-deployable' is optional. indicates whether the update is independently deployable.. The parameter '--no-validation' is optional. disables client-side json schema validation of the import manifest content.. The parameter '--related-file' is optional. space-separated key=value pairs corresponding to 'files[*].relatedfiles' element properties. a --related-file entry will be associated to the closest --file entry if it exists. the following keys are supported: `path` [required] local file path to related update file, `properties` (in-line json object passed to the download handler). --related-file can be used 1 or more times.. 