CLA_BACKEND PROD: increase snapshot retention period for cla backend DB

[willclarke (willc-work)]

we are dealing with a data loss incident that occurred last thursday evening, the current snapshot is due to be deleted in the next 24 hours and we want to keep it around a bit longer until we are sure we have restored the data. My assumption is that this PR will ensure the snapshot remains available until next thursday.

[Sablu M (sablumiah)]

Terraform Plan Summary

Terraform Plan: 0 to be created, 0 to be destroyed, 7 to be updated, 2 to be replaced and 79 unchanged.

Resources to update:

! kubernetes_secret.cla_backend_intermediary
! kubernetes_secret.cla_backend_snapshot_restore
! module.cla_backend_intermediary.aws_iam_policy.irsa[0]
! module.cla_backend_metabase_rds.aws_db_parameter_group.custom_parameters
! module.cla_backend_rds_postgres_14.aws_db_instance.rds
! module.cla_backend_snapshot_restore.aws_iam_policy.irsa[0]
! pingdom_check.laa-cla-backend-pingdom

Resources to replace:

-+ module.cla_backend_intermediary.aws_db_instance.rds
-+ module.cla_backend_snapshot_restore.aws_db_instance.rds

[Sablu M (sablumiah)]

This PR CANNOT be auto approved and requires manual approval from the Cloud Platform team.
Reason:
🕵️‍♂️ Manual review required: OPA auto approve policy checks did not pass.

Test	Passed?	Reason
allowlist	❌	This PR includes changes to modules / resources which are not on the allowlist, so we can't auto approve these changes. Please request a Cloud Platform team member's review in #ask-cloud-platform
ecr	✅	Valid ECR related terraform changes
hmpps-template	✅	Valid hmpps template related terraform changes
irsa	✅	Valid irsa related terraform changes
kubernetes_secret	✅	Valid K8s secret related terraform changes
rds	✅	Valid RDS module related terraform changes
secrets_manager	✅	Valid secrets manager related terraform changes
service_pod	✅	Valid Service pod related changes
sns	✅	Valid sns related terraform changes

Please raise it in #ask-cloud-platform Slack channel.

[Sablu M (sablumiah)]

Terraform Plan Summary

Terraform Plan: 0 to be created, 0 to be destroyed, 7 to be updated, 2 to be replaced and 79 unchanged.

Resources to update:

! kubernetes_secret.cla_backend_intermediary
! kubernetes_secret.cla_backend_snapshot_restore
! module.cla_backend_intermediary.aws_iam_policy.irsa[0]
! module.cla_backend_metabase_rds.aws_db_parameter_group.custom_parameters
! module.cla_backend_rds_postgres_14.aws_db_instance.rds
! module.cla_backend_snapshot_restore.aws_iam_policy.irsa[0]
! pingdom_check.laa-cla-backend-pingdom

Resources to replace:

-+ module.cla_backend_intermediary.aws_db_instance.rds
-+ module.cla_backend_snapshot_restore.aws_db_instance.rds

[Sablu M (sablumiah)]

This PR CANNOT be auto approved and requires manual approval from the Cloud Platform team.
Reason:
🕵️‍♂️ Manual review required: OPA auto approve policy checks did not pass.

Test	Passed?	Reason
allowlist	❌	This PR includes changes to modules / resources which are not on the allowlist, so we can't auto approve these changes. Please request a Cloud Platform team member's review in #ask-cloud-platform
ecr	✅	Valid ECR related terraform changes
hmpps-template	✅	Valid hmpps template related terraform changes
irsa	✅	Valid irsa related terraform changes
kubernetes_secret	✅	Valid K8s secret related terraform changes
rds	✅	Valid RDS module related terraform changes
secrets_manager	✅	Valid secrets manager related terraform changes
service_pod	✅	Valid Service pod related changes
sns	✅	Valid sns related terraform changes

Please raise it in #ask-cloud-platform Slack channel.