Settle on and build out PSArm execution experience

PowerShell / PSArm

PSArm is a PowerShell module that provides a PowerShell-embedded domain-specific language (DSL) for Azure Resource Manager (ARM) templates

MIT License

78 stars 19 forks source link

Settle on and build out PSArm execution experience #33

Closed rjmholt closed 3 years ago

rjmholt commented 4 years ago

Key questions:

Should the Arm keyword simply define a declaration, or should it emit a template to a file? Should we need to assign it to a variable to use or should we lean on convention to make it just do the right thing?
Is there value in something like an .arm.ps1 file extension?
What other user-facing (i.e. non-DSL) cmdlets do we need to supply?
- A "watch"-style command to get JSON on the fly?
- A "deploy" command? Currently served by reusing New-AzResourceGroupDeployment

rjmholt commented 3 years ago

Settled on this in https://github.com/PowerShell/PSArm/pull/76.

The experience is that files use the .PSArm.ps1 extension and Publish-ArmTemplate -Path <path> runs on those files (or directories, recursively), executing the scripts and collecting the results to instantiate as a nested ARM template to be deployed with the chosen tool.