Parameterise backup policy and instance naming across resource types#142
Merged
narendra-asadi merged 12 commits intomainfrom Feb 10, 2026
Merged
Parameterise backup policy and instance naming across resource types#142narendra-asadi merged 12 commits intomainfrom
narendra-asadi merged 12 commits intomainfrom
Conversation
johncollinson2001
approved these changes
Feb 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR adds support for configurable naming templates for backup policies and backup instances across all backup submodules (blob storage, managed disk, and PostgreSQL flexible server).
The change is fully backwards-compatible. Existing consumers continue to get the same resource names by default, while teams with pre-existing resources can pass templates to avoid destructive renames. This unblocks safe adoption of the module by teams migrating from inline Terraform resources.
Type of change
Please check the relevant options:
🔲 New feature (a change which adds functionality)
🔲 Bug fix (a change which fixes an issue)
🔲 Refactoring (code cleanup or optimisation)
🔲 Testing (new tests, or improvements to existing tests)
🔲 Pipelines (changes to pipelines and workflows)
🔲 Documentation (changes to documentation)
🔲 Other (something that's not listed here - please explain)
Checklist
Please check the relevant options:
🔲 My code aligns with the style of this project
🔲 I have added comments in hard to understand areas
🔲 I have added tests that prove my change works
🔲 I have updated the documentation
🔲 If merging into main, I'm aware that the PR should be squash merged with a commit message that adheres to the semantic release format
Additional Information
Please provide any additional information or context related to this pull request.