Naming convention error when deploying IoT Operations (az iot ops init)

[JzNotJz]

Naming convention error when deploying IoT Operations (az iot ops init)

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.

[digimaun]

Hi @JzNotJz, it looks like your instance name is too long by 1 character. You can use --dp-instance to provide a shorter custom name to the data processor instance. For future reference init documentation is here https://learn.microsoft.com/en-us/cli/azure/iot/ops?view=azure-cli-latest#az-iot-ops-init (which is same content as when appending --help/-h to the command).

[JzNotJz]

Hi @digimaun thanks for prompt response. I followed the QuickStarts of IoT Operations Preview. Would you please confirm that if it would cause other problem if I hardcoded the instance name for a shorter one? I would prefer someone to update the Codespaces so that others would not run into the same problem in the future. Please advise. Thanks.

[digimaun]

There should be no issue using a different, shorter, instance name. The default instance name is a convention rather than a rule. Acknowledged on updating the Codespaces docs.