Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--hub-name seems to be mandatory parameter but is listed as an optional #18701

Closed
jspaith opened this issue Jun 30, 2021 · 5 comments
Closed
Labels
IoT/CLI IoT IotHub az iot Service Attention This issue is responsible by Azure service team.

Comments

@jspaith
Copy link

jspaith commented Jun 30, 2021

On this page, --hub-name is listed under the optional parameters. I think its mandatory, although maybe via the --login or something it wouldn't be needed if used instead? It still feels that one of them is required.

I looked at here also listed hub-name as optional but I'm almost positive its required, so if what I'm raising is indeed an issue and not my az tool naivete then should look at other places.

My repro of not having --hub-name

C:\developer\local> az iot hub module-identity create --device-id $deviceId --module-id $filterModule
DLL load failed while importing win32file: The specified module could not be found.
Please provide an IoT Hub entity name (via the '--hub-name' or '-n' parameter) or IoT Hub connection string via --login...

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jun 30, 2021
@vilit1
Copy link
Contributor

vilit1 commented Jun 30, 2021

This is something by design: we require users to provide either --hub-name or --login parameters so the --hub-name is not required as long as --login is provided.

We will improve the help section to make this distinction clearer.

@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jul 1, 2021
@yonzhan yonzhan added needs-triage This is a new issue that needs to be triaged to the appropriate team. Service Attention This issue is responsible by Azure service team. labels Jul 1, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jul 1, 2021
@ghost
Copy link

ghost commented Jul 1, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @rkmanda, @chieftn.

Issue Details

On this page, --hub-name is listed under the optional parameters. I think its mandatory, although maybe via the --login or something it wouldn't be needed if used instead? It still feels that one of them is required.

I looked at here also listed hub-name as optional but I'm almost positive its required, so if what I'm raising is indeed an issue and not my az tool naivete then should look at other places.

My repro of not having --hub-name

C:\developer\local> az iot hub module-identity create --device-id $deviceId --module-id $filterModule
DLL load failed while importing win32file: The specified module could not be found.
Please provide an IoT Hub entity name (via the '--hub-name' or '-n' parameter) or IoT Hub connection string via --login...

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Author: jspaith
Assignees: -
Labels:

IoT, IoT/CLI, IotHub, Service Attention, needs-triage

Milestone: -

@yonzhan
Copy link
Collaborator

yonzhan commented Jul 1, 2021

route to service team

@vilit1
Copy link
Contributor

vilit1 commented Oct 26, 2021

The help has been updated to inform users to provide either --hub-name or --login parameters, under the Iot Hub Identifier Arguments. The parameter --hub-name is not required as long as --login is provided.

Please update to the latest version of azure-iot

@digimaun
Copy link
Member

We also have this related investigation to improve devEx on this front Azure/azure-iot-cli-extension#398.

Closing issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IoT/CLI IoT IotHub az iot Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants