Expansion defaults for PSRule for Azure v2

[BernieWhite]

When using PSRule for Azure to test Infrastructure as Code, enabling expansion for parameter files and Bicep code is a key step. Today PSRule for Azure defaults to:

• Expansion of parameter files is disabled by default and can be enabled by setting AZURE_PARAMETER_FILE_EXPANSION to true.
• Expansion of Bicep code is disabled by default and can be enabled by setting AZURE_BICEP_FILE_EXPANSION to true.

We feel this is a point of confusion for people initially picking up PSRule for Azure and we would like to get your feedback on if we should change the defaults for PSRule for Azure v2 which we are working towards.

What won't change

We have no plans to take the option away from being able to enable or disable expansion for either parameter files or Bicep code it is a choice that will remain for v2 and the foreseeable future.

This is about the changing the defaults, and if this would make it harder or easier to use PSRule for Azure.

Expansion for parameter files and Bicep code on by default

We feel that, all people using PSRule within a continuous integration pipeline want expansion enabled, however both parameter files and Bicep repository typically need some configuration to take advantage of all tests.

• Parameter files need to be linked (in most cases) to templates or Bicep code.
• Bicep modules with required parameter need to be ignored and deployments/ tests used instead.

Enabling by default may lead to more pipelines errors that need to be resolved initially.

[BernieWhite]

We feel that currently is not enough support either way for making this change so we have decided to make no changes to this behaviour in v2.