PSArm

PSArm copied to clipboard

Some questions here are: - What if two templates have the same parameter name? (Default assumption: they share a value) - What's a nice way to pass in expressions here?

rjmholt

Variables definitions are made available to root template

2

If you define an [ArmParameter] and it has no default value, it will be created in the nested template but since it isn't in the root template there is no...

rdbartram

Make resource referencing easier

4

Today to reference one resource from another I have to embed the ARM the hard way: ```powershell Resource 'MyResource' -Provider Microsoft.Network -Type 'virtualNetworks/subnets' -ApiVersion 2019-11-01 { properties { addressPrefix 10.0.0.0/24...

rjmholt

Make available option to include outputs in root template

2

Right now when you use outputs, they are included in nested template but there is seemingly no way to output from the root template so they are available to the...

rdbartram

Aliases take high precedence and can be interfered with globally. Wrapper functions make parameters harder but also mean that core keywords and resource property keywords will play together nicely

rjmholt

This should fail if multiple template objects are found

rjmholt

For example: ```json "mode": "All", "policyRule": { "if": { "allOf": [ { "field": "type", "equals": "..." }, { "anyOf": [ { "field": "location", "notEquals": "..." }, { "field": "name", "notEquals":...

rjmholt

ConvertFrom-ArmTemplate and ConvertTo-PSArm should recognise nested ARM templates and write them with the appropriate objects and keywords

rjmholt

Currently they look like: ```powershell $schema '...' ``` Which is invalid

rjmholt

rjmholt