Add foundation for extension config assignment syntax in bicepparam files and extensionConfigs on module declarations

[kalbert312]

Contributing a Pull Request

If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check. Once you are done and ready to submit your PR, run through the relevant checklist below.

Contributing a feature

• I have opened a new issue for the proposal, or commented on an existing one, and ensured that the Bicep maintainers are good with the design of the feature being implemented: Foundation for Integration of extension resources with deployment stacks. bicep-reps#6

• I have included "Fixes #{issue_number}" in the PR description, so GitHub can link to the issue and close it when the PR is merged

• I have appropriate test coverage of my new feature

• I have a resource name property equal to "name"

• If applicable, I have set the location property to location: /*${<id>:location}*/'location' (not resourceGroup().location) where <id> is a placeholder id, and added param location string to the test's main.bicep file so that the resulting main.combined.bicep file used in the tests compiles without errors

• I have verified that the snippet deploys correctly when used in the context of an actual bicep file

  e.g.

  resource aksCluster 'Microsoft.ContainerService/managedClusters@2021-03-01' = {
    name: 'name'

Microsoft Reviewers: Open in CodeFlow

PR Overview

This PR adds foundational support for extension config assignment syntax while enhancing test coverage and updating related diagnostics.

• Adds new integration tests for module extension configurations.
• Updates baseline samples and CLI integration tests for improved error assertions.
• Refactors module diagnostics and template generation methods in integration tests.

Reviewed Changes

File	Description
src/Bicep.Core.IntegrationTests/ExtensibilityTests.cs	Introduces tests for valid and invalid extension config assignments.
src/Bicep.Core.Samples/DataSets.cs	Adds a new DataSet sample ("Extensions_CRLF") for extension-related scenarios.
src/Bicep.Cli.IntegrationTests/BuildParamsCommandTests.cs	Adds additional non-null assertions and updates expected diagnostic validations.
src/Bicep.Core.Samples/BaselineData_Bicepparam.cs	Updates the baseline data list to include extension-related parameters files.
src/Bicep.Core.IntegrationTests/ModuleTests.cs	Refactors diagnostic retrieval and template generation to use updated API methods.

Copilot reviewed 69 out of 69 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/Bicep.Core.Samples/DataSets.cs:21

• [nitpick] The naming 'Extensions_CRLF' could be more descriptive; consider adding a comment to clarify its intent (e.g., indicating that it targets tests involving CRLF line endings) or renaming it for better clarity.

public static DataSet Extensions_CRLF => CreateDataSet();

[kalbert312]

Not certain why this is separate from the rest.

[kalbert312]

Property emission not yet implemented.

[github-actions]

Test this change out locally with the following install scripts (Action run 13731067870)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 13731067870

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 13731067870"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 13731067870

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 13731067870"

[github-actions]

Dotnet Test Results

    78 files   -     39      78 suites   - 39   31m 17s ⏱️ - 15m 31s
11 996 tests +    47  11 996 ✅ +    47  0 💤 ±0  0 ❌ ±0 
27 750 runs   - 13 690  27 750 ✅  - 13 690  0 💤 ±0  0 ❌ ±0 

Results for commit 4cefd1b. ± Comparison against base commit 450ba67.

This pull request removes 1792 and adds 671 tests. Note that renamed tests count towards both.

		nestedProp1: 1
		nestedProp2: 2
		prop1: true
		prop2: false
	1
	2
	\$'")
	prop1: true
	prop2: false
…

Bicep.Cli.IntegrationTests.BuildCommandTests ‑ Build_Valid_SingleFile_WithTemplateSpecReference_ShouldSucceed_Extensions_CRLF
Bicep.Cli.IntegrationTests.BuildCommandTests ‑ Build_Valid_SingleFile_WithTemplateSpecReference_ToStdOut_ShouldSucceed_Extensions_CRLF
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ Build_Valid_Params_File_Should_Succeed (Files/baselines_bicepparam/Extensions/parameters.bicepparam)
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ Build_Valid_Params_File_ToStdOut_Should_Succeed (Files/baselines_bicepparam/Extensions/parameters.bicepparam)
Bicep.Cli.IntegrationTests.BuildParamsCommandTests ‑ Build_Valid_Params_File_To_Outdir_Should_Succeed (Files/baselines_bicepparam/Extensions/parameters.bicepparam)
Bicep.Cli.IntegrationTests.FormatCommandTests ‑ Format_SampleBicepFile_MatchesFormattedSample_Extensions_CRLF
Bicep.Cli.IntegrationTests.FormatCommandTests ‑ Format_SampleBicepParam_MatchesFormattedSample (Files/baselines_bicepparam/Extensions/parameters.bicepparam)
Bicep.Cli.IntegrationTests.PublishCommandTests ‑ Extensions_CRLF, with docUri, publishing source
Bicep.Cli.IntegrationTests.PublishCommandTests ‑ Extensions_CRLF, without docUri, not publishing source
Bicep.Cli.IntegrationTests.PublishCommandTests ‑ Publish_ValidArmTemplateFile_AllValidDataSets_ShouldSucceed_Extensions_CRLF
…

♻️ This comment has been updated with latest results.

[kalbert312]

Not sure why the symbol isn't showing up.

[kalbert312]

I'm not sure if this is needed. This syntax is only usable in param files. I think referencing assignments from other assignments should be permissible, but that's for a later PR.