What is the problem this feature will solve?
We have two types of data we want to backup, live and historic, these have different backup schedule and retention periods.
There doesn't seem to be the ability to create two backup plans pointing at the same vault using the blueprint.
What is the feature that you are proposing to solve the problem?
Change the variable backup_plan_config to be a list of configuration objects.
So we could have multiple backup plans (and their associated aws_backup_selection resources) targeting the one vault.
What alternatives have you considered?
Amending the blueprint code to allow it to be called multiple times, creating multiple vaults per backup/ retention requirements.
Code of Conduct
Sensitive Information Declaration
What is the problem this feature will solve?
We have two types of data we want to backup, live and historic, these have different backup schedule and retention periods.
There doesn't seem to be the ability to create two backup plans pointing at the same vault using the blueprint.
What is the feature that you are proposing to solve the problem?
Change the variable
backup_plan_configto be a list of configuration objects.So we could have multiple backup plans (and their associated
aws_backup_selectionresources) targeting the one vault.What alternatives have you considered?
Amending the blueprint code to allow it to be called multiple times, creating multiple vaults per backup/ retention requirements.
Code of Conduct
Sensitive Information Declaration