Conversation
|
@pamelafox - Could you please install the build from this PR and see if it works for you? |
wbreza
left a comment
There was a problem hiding this comment.
Looks great, just added a couple points that we should agree on before finishing up.
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
|
I just tried it out, worked great! Much nicer than my grepsed horror. |
@pamelafox , can you share the way you are using I'm curious to understand what's the use case and if the |
|
@vhvb1989 From a script that's used in hooks (or outside of hooks)- |
|
It would also be useful in CI, like this workflow from @tonybaloney - |
|
@pamelafox , thanks for sharing. So, the script is typically expected to be called by azd from a hook, but you want to allow folks to run the script w/o calling either Are you not using What if From my POV, I would much prefer if the scripts pull the value directly from the system environment and having azd to inject that env during the script execution. That's for the benefit of using the script w/o azd as well. |
That's an interesting approach! |
|
@vhvb1989 Your summary is correct, I want to be able to run the scripts separately, versus all three at once that the hook does. I think it'd be nice for |
* Test aks * Add get-value * Undo aks string * Remove formatter * Add tests
Adds
azd env get-value keyNamecommand.Fixes #3906