US 31189 - Add BICEPPARAM files to modules

[4pplied]

Overview/Summary

PR to add BICEPPARAM files in co-existence with JSON parameter files. Also added Code snippets into Markdowns.

AB#31189

This PR fixes/adds/changes/removes

1. Added BICEPPARAM files into the same folder as the JSON parameters for each respective module

Breaking Changes

1. N/A

Testing Evidence

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[oZakari]

Thanks @appli3d, I'll go over this tomorrow morning.

[picccard]

Wow great stuff @appli3d!

Have you done any testing with bicepparam files located in the config/custom-parameters folder as per the accelerator folder-structure?

Any bicepparam there would have to start with using '../../upstream-versions/v0.16.6/infra-as-code/...'
So how would upgrading to any newer release be handled? All bicepparams would be manually updated or could the env:UPSTREAMVERSION be used there?

[oZakari]

Looking through some of the tests to make sure we don't need exclude or adjust any existing tests but so far looks good. @appli3d

[oZakari]

Hi @picccard! We are looking in transitioning the Accelerator to the bicepparam files in the next couple of months. You should be able to transition your existing json parameter files within the Accelerator, but would have to adjust the using statement from the ones included in this PR.

[oZakari]

Holding off on merging this until we sort the Accelerator out and I will keep in-sync until then.

[oZakari]

Holding off on Bicep params until we get updates from PG on whether they decide to remove the using statements.