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

Allow on build to run Powershell Az commands to get information #417

Closed
slavizh opened this issue Sep 1, 2020 · 7 comments
Closed

Allow on build to run Powershell Az commands to get information #417

slavizh opened this issue Sep 1, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@slavizh
Copy link
Contributor

slavizh commented Sep 1, 2020

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

var subscriptions = Get-AzSubscription

Also should apply for any PowerShell command.

@slavizh slavizh added the enhancement New feature or request label Sep 1, 2020
@ghost ghost added the Needs: Triage 🔍 label Sep 1, 2020
@Satak
Copy link

Satak commented Sep 9, 2020

Great idea! Full support for this. This would make Bicep so much better than the ARM.

@alex-frankel alex-frankel changed the title Allow on build to run Az commands to get information Allow on build to run Powershell Az commands to get information Sep 9, 2020
@alex-frankel
Copy link
Collaborator

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.

@Satak
Copy link

Satak commented Sep 10, 2020

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.

@slavizh
Copy link
Contributor Author

slavizh commented Sep 10, 2020

@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.

@cognitox
Copy link

Is there any update on this feature yet?

@kilasuit
Copy link

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

@alex-frankel
Copy link
Collaborator

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.

@ghost ghost locked as resolved and limited conversation to collaborators May 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants