Skip to content
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

Add continuousBackupConfig and continuousBackupInfo to AlloyDB cluster #8406

Merged
merged 16 commits into from
Aug 1, 2023

Conversation

GoogleMarcfont
Copy link
Member

Add continuousBackupConfig and continuousBackupInfo to AlloyDB cluster.

Fixes hashicorp/terraform-provider-google#15110
b/291745106
Part of hashicorp/terraform-provider-google#13757
b/284523617

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)

AlloyDB: added `continuous_backup_config` and `continuous_backup_info` fields to `cluster` resource

@modular-magician
Copy link
Collaborator

Hello! I am a robot. It looks like you are a community contributor. @melinath, 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.

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 838 insertions(+), 9 deletions(-))
Terraform Beta: Diff ( 4 files changed, 838 insertions(+), 9 deletions(-))
TF Conversion: Diff ( 3 files changed, 73 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 5 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2877
Passed tests 2566
Skipped tests: 299
Affected tests: 12

Action taken

Found 12 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccComputeFirewallPolicyRule_multipleRules|TestAccAlloydbCluster_continuousBackup_updateDisable|TestAccAlloydbCluster_continuousBackup_updateRecoveryWindowDays|TestAccAlloydbCluster_AutomatedBackupPolicyHandlesMidnight|TestAccAlloydbCluster_continuousBackup_noChangeIfRemoved|TestAccAlloydbCluster_alloydbClusterFullExample|TestAccAlloydbCluster_update|TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable|TestAccAlloydbCluster_maximumFields|TestAccAlloydbCluster_continuousBackup_update_noChangeIfDefaultsSet|TestAccAlloydbCluster_continuousBackup_enabledByDefault|TestAccContainerAwsNodePool_BetaBasicHandWritten

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbCluster_continuousBackup_updateDisable[Debug log]
TestAccAlloydbCluster_continuousBackup_updateRecoveryWindowDays[Debug log]
TestAccAlloydbCluster_AutomatedBackupPolicyHandlesMidnight[Debug log]
TestAccAlloydbCluster_continuousBackup_noChangeIfRemoved[Debug log]
TestAccAlloydbCluster_alloydbClusterFullExample[Debug log]
TestAccAlloydbCluster_update[Debug log]
TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable[Debug log]
TestAccAlloydbCluster_maximumFields[Debug log]
TestAccAlloydbCluster_continuousBackup_update_noChangeIfDefaultsSet[Debug log]
TestAccAlloydbCluster_continuousBackup_enabledByDefault[Debug log]

Rerun these tests in REPLAYING mode to catch issues

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$


$\textcolor{red}{\textsf{Tests failed during RECORDING mode:}}$
TestAccComputeFirewallPolicyRule_multipleRules[Error message] [Debug log]
TestAccContainerAwsNodePool_BetaBasicHandWritten[Error message] [Debug log]

$\textcolor{red}{\textsf{Please fix these to complete your PR.}}$
View the build log or the debug log for each test

Copy link
Member

@melinath melinath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a few questions and change requests below.

mmv1/products/alloydb/Cluster.yaml Outdated Show resolved Hide resolved
mmv1/products/alloydb/Cluster.yaml Show resolved Hide resolved
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
Terraform Beta: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
TF Conversion: Diff ( 3 files changed, 73 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 5 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2915
Passed tests 2610
Skipped tests: 302
Affected tests: 3

Action taken

Found 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccContainerAwsNodePool_BetaBasicHandWritten|TestAccAlloydbCluster_continuousBackup_update|TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbCluster_continuousBackup_update[Debug log]
TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable[Debug log]

Rerun these tests in REPLAYING mode to catch issues

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$


$\textcolor{red}{\textsf{Tests failed during RECORDING mode:}}$
TestAccContainerAwsNodePool_BetaBasicHandWritten[Error message] [Debug log]

$\textcolor{red}{\textsf{Please fix these to complete your PR.}}$
View the build log or the debug log for each test

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
Terraform Beta: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
TF Conversion: Diff ( 3 files changed, 73 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 5 insertions(+))

Copy link
Member

@melinath melinath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall, just needs one change to the kms tests.

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2915
Passed tests 2612
Skipped tests: 302
Affected tests: 1

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccContainerAwsNodePool_BetaBasicHandWritten

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

$\textcolor{red}{\textsf{Tests failed during RECORDING mode:}}$
TestAccContainerAwsNodePool_BetaBasicHandWritten[Error message] [Debug log]

$\textcolor{red}{\textsf{Please fix these to complete your PR.}}$
View the build log or the debug log for each test

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
Terraform Beta: Diff ( 4 files changed, 708 insertions(+), 9 deletions(-))
TF Conversion: Diff ( 3 files changed, 73 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 5 insertions(+))

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 4 files changed, 720 insertions(+), 9 deletions(-))
Terraform Beta: Diff ( 4 files changed, 720 insertions(+), 9 deletions(-))
TF Conversion: Diff ( 3 files changed, 73 insertions(+), 3 deletions(-))
TF OiCS: Diff ( 1 file changed, 5 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 2917
Passed tests 2613
Skipped tests: 302
Affected tests: 2

Action taken

Found 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
TestAccContainerAwsNodePool_BetaBasicHandWritten|TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccAlloydbCluster_continuousBackup_CMEKIsUpdatable[Debug log]

Rerun these tests in REPLAYING mode to catch issues

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$


$\textcolor{red}{\textsf{Tests failed during RECORDING mode:}}$
TestAccContainerAwsNodePool_BetaBasicHandWritten[Error message] [Debug log]

$\textcolor{red}{\textsf{Please fix these to complete your PR.}}$
View the build log or the debug log for each test

Copy link
Member

@melinath melinath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@melinath melinath merged commit ed8f2d4 into GoogleCloudPlatform:main Aug 1, 2023
8 checks passed
DanielRieske pushed a commit to bschaatsbergen/magic-modules that referenced this pull request Aug 2, 2023
GoogleCloudPlatform#8406)

* Properly handle ABP midnight (hours = 0)

* Add ExpectNonEmptyPlan to test

* Add continuous backup config to alloydb cluster

* add more unit tests

* Adding more tests

* Fix cluster.yaml lint

* Add default value and update cmek test

* Update test to use kms key bootstrapping util

* condense update tests

* Change encryptionType output field to string

* use two different keys

* Only update encryption in CBR
simonebruzzechesse pushed a commit to simonebruzzechesse/magic-modules that referenced this pull request Aug 3, 2023
GoogleCloudPlatform#8406)

* Properly handle ABP midnight (hours = 0)

* Add ExpectNonEmptyPlan to test

* Add continuous backup config to alloydb cluster

* add more unit tests

* Adding more tests

* Fix cluster.yaml lint

* Add default value and update cmek test

* Update test to use kms key bootstrapping util

* condense update tests

* Change encryptionType output field to string

* use two different keys

* Only update encryption in CBR
jeperetz pushed a commit to jeperetz/magic-modules that referenced this pull request Aug 10, 2023
GoogleCloudPlatform#8406)

* Properly handle ABP midnight (hours = 0)

* Add ExpectNonEmptyPlan to test

* Add continuous backup config to alloydb cluster

* add more unit tests

* Adding more tests

* Fix cluster.yaml lint

* Add default value and update cmek test

* Update test to use kms key bootstrapping util

* condense update tests

* Change encryptionType output field to string

* use two different keys

* Only update encryption in CBR
ron-gal pushed a commit to ron-gal/magic-modules that referenced this pull request Aug 17, 2023
GoogleCloudPlatform#8406)

* Properly handle ABP midnight (hours = 0)

* Add ExpectNonEmptyPlan to test

* Add continuous backup config to alloydb cluster

* add more unit tests

* Adding more tests

* Fix cluster.yaml lint

* Add default value and update cmek test

* Update test to use kms key bootstrapping util

* condense update tests

* Change encryptionType output field to string

* use two different keys

* Only update encryption in CBR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support AlloyDB continuous backup
3 participants