-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Support for Single Template with Multiple Parameter Files #836
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jefajers
added
wiki-doc
Improvements or additions to documentation
enhancement
New feature or request
area/powershell
labels
Dec 8, 2023
daltondhcp
previously approved these changes
Dec 11, 2023
🚀 |
Xitric
reviewed
Dec 11, 2023
daltondhcp
approved these changes
Dec 18, 2023
Xitric
approved these changes
Dec 19, 2023
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/powershell
enhancement
New feature or request
wiki-doc
Improvements or additions to documentation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview/Summary
This PR adds support for single template with multiple parameter file associations resulting in multiple deployments and closes #831.
The parameter file association allows for many-to-one relationships between parameter file and template and each relationship represents a unique deployment.
This behavior's is controlled with three new settings
Core.AllowMultipleTemplateParameterFiles
,Core.DeployAllMultipleTemplateParameterFiles
andCore.MultipleTemplateParameterFileSuffix
read more in the wiki or head over to faq.This feature is disabled by default, to enable this feature set
Core.AllowMultipleTemplateParameterFiles
totrue
.It is optional to change
Core.DeployAllMultipleTemplateParameterFiles
, if you want changes made to the base template to be treated as separate deployments for each corresponding parameter file.It is optional to change
Core.MultipleTemplateParameterFileSuffix
, if you want a different filename identifier thanx
update this setting as well.This PR fixes/adds/changes/removes
Frequently-Asked-Questions.md
Settings.md
Initialize-AzOpsEnvironment.ps1
Invoke-AzOpsPush.ps1
Core.ps1
ConvertFrom-AzOpsBicepTemplate.ps1
New-AzOpsDeployment.ps1
Set-AzOpsWhatIfOutput.ps1
Strings.psd1
Repository.Tests.ps1
rtmultibase.bicep
rtmultibase.x123.parameters.json
rtmultibase.xabc.bicepparam
deployallrtbase.bicep
deployallrtbase.x123.parameters.json
deployallrtbase.xabc.bicepparam
Breaking Changes
Testing Evidence
Automated testing included in PR and in additon to that manual testing has been performed with custom
.bicep
,.json
,.parameters.json
and.bicepparam
files in conjunjtion with different Azure Policy deployments.As part of this Pull Request I have
main
branch