Open agpt8 opened 1 year ago
Any updates on this? I can still reproduce this issue on azd version 1.5.0 (commit 012ae734904e0c376ce5074605a6d0d3f05789ee)
Hello @agpt8, thank you for reporting this issue. We'll plan for a fix soon (latest features for 1.5.0 have kept us busy :)
Have you used azd completions before? I'd like to understand what's the common use-case. Would you expect to generate completion after each azd-release to update your shell?
I have used azd completions for powershell and bash. While I knew how to add those completions to my powershell profiles file, wanted to know if azd recommends some other way to do that or if it had any other mechanims to provide the completions for that shell. Which is why I used the azd completion <shell> --help
hoping that it would provide instructions on how to use those completions or atleast some helpful info.
But the command outputs generic help content instead of contents on completions. I would like it to show me what all completions azd offers, how to add them to my shell profile, how to use those completions and any other helpful content that might come in handy with it.
Output from
azd version
azd version 1.4.1 (commit 1cbed85cf47ed235b5ed31868eda79619525bfcc)Describe the bug Under the shell completion section of the README, it says to get instructions for specific shell, run
azd completion <shell> --help
(substituting actual name here as the output is same for each shell).However, instead of printing specific instructions for installing completions for each shell, the generic help (which can also be viewed with
azd --help
is printed.To Reproduce
azd --help
and see the output.azd completion <your shell name> --help
and see the output.Expected behavior The output of the command
azd completion <your shell name> --help
should provide specific instruction to install completion for that shell and not print the generic help which is the same output asazd --help
.Environment Information on your environment:
Additional context This issue is encountered on a fresh install of azd and the system itself. Login process has not been initiated yet, though I don't think it should affect it in anyway. Update: The output is the same as stated above after login