-
Notifications
You must be signed in to change notification settings - Fork 747
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
Allow on build to run Powershell Az commands to get information #417
Comments
Great idea! Full support for this. This would make Bicep so much better than the ARM. |
Stan, presumably this would not be limited to Az right? If I can run the Az module, I should be able to run any arbitrary powershell at that point. |
Yes this would be ideal, just full Powershell support so you can import and use any cmdlet, even your own. |
@alex-frankel yes. I have added one last sentence that it should apply to any PowerShell cmdlet thus module. Of course there are always things that you cannot do at build so for those scenarios you will still rely on deploymentScripts. |
Is there any update on this feature yet? |
This would be great and was one of the leading reasons why I was excited by PSARM as you'd have it already for free |
I don't see us getting to this feature anytime soon, if ever. We can revisit if there are a lot of requests/feedback asking for this. |
Is your feature request related to a problem? Please describe.
Allow on build to run Az commands to get information
Describe the solution you'd like
When bicep build is run the Az PowerShell commands should be run that are in the .bicep file. The information from the commands you can put into variables, outputs and parameters. For example
Also should apply for any PowerShell command.
The text was updated successfully, but these errors were encountered: