Skip to content

Conversation

@varadvjoshi99
Copy link

@varadvjoshi99 varadvjoshi99 commented Jan 2, 2026

Add support for restoring AlloyDB clusters via BackupDR backups and PITR via BackupDR data sources.

To restore a cluster directly from a backup, add the following line to your AlloyDB cluster:

restore_backupdr_backup_source {
backup =
}
To restore a cluster via PITR, add the following lines to your AlloyDB cluster:

restore_backupdr_pitr_source {
data_source =
point_in_time = <timestamp in RFC 3339 format>
}
Part of hashicorp/terraform-provider-google#13757. I am not fully closing the issue because I did not yet add support for data calls for backups as requested.

If this PR is for Terraform, I acknowledge that I have:

  • Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).

  • Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).

  • Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests.

  • Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).

  • Read Write release notes before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

alloydb: added `restoreBackupdrBackupSource`, `restoreBackupdrPitrSource`, and `backupdrBackupSource` fields to `google_alloydb_cluster` resource

@google-cla
Copy link

google-cla bot commented Jan 2, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@modular-magician modular-magician added the awaiting-approval Pull requests that need reviewer's approval to run presubmit tests label Jan 2, 2026
@varadvjoshi99 varadvjoshi99 changed the title Alloydb integration AlloyDB BackupDR integration support Jan 2, 2026
@varadvjoshi99 varadvjoshi99 marked this pull request as ready for review January 2, 2026 11:26
@github-actions github-actions bot requested a review from rileykarson January 2, 2026 11:27
@github-actions
Copy link

github-actions bot commented Jan 2, 2026

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

Googlers: For automatic test runs see go/terraform-auto-test-runs.

@rileykarson, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

@varadvjoshi99
Copy link
Author

Hi @rileykarson, please take a look, Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-approval Pull requests that need reviewer's approval to run presubmit tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants