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

New Command to deploy Bicep file to ARM #226

Open
PalmEmanuel opened this issue Nov 20, 2021 · 2 comments
Open

New Command to deploy Bicep file to ARM #226

PalmEmanuel opened this issue Nov 20, 2021 · 2 comments
Labels

Comments

@PalmEmanuel
Copy link
Member

Is your feature request related to a problem? Please describe.
After some offline discussion, I'd like to suggest that we implement a command to be able to deploy files directly using PSBicep, instead of creating an implicit dependency for the user by relying on the Azure CLI or PowerShell Module (or Azure portal).

Describe the solution you'd like
A new command such as New-BicepDeployment with a scope variabel (or several commands based on scope, matching the Az module style).

Additional context
The reasoning behind the suggestion is that both the CLI and especially the PowerShell module Az are quite large to download if you're running the deployment from something like a pipeline or container. Only having to install PSBicep would improve the consumer experience, and we have the option of adding functionality such as Build and Restore directly into our Deployment command.

Since we can handle Bicep code as strings, it would also allow us to be able to deploy directly from an online hosting such as the raw file of a GitHub repository without creating a file.

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-rest

@PalmEmanuel PalmEmanuel added the enhancement New feature or request label Nov 20, 2021
@StefanIvemo
Copy link
Member

Should we change the dependency label to AzAuth?

@PalmEmanuel
Copy link
Member Author

Agreed, implementing AzAuth and making a deployment to the REST API in the module is probably the way we want to proceed with the command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants