Add examples for AlloyDB Major Version Upgrade

[GauravJain21]

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

alloydb: add examples for AlloyDB Major Version Upgrade for `google_alloydb_cluster` resource.

[github-actions]

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

@slevenick, 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]

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.

google provider: Diff ( 2 files changed, 256 insertions(+))
google-beta provider: Diff ( 2 files changed, 256 insertions(+))
Open in Cloud Shell: Diff ( 8 files changed, 290 insertions(+))

[modular-magician]

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.

google provider: Diff ( 2 files changed, 256 insertions(+))
google-beta provider: Diff ( 2 files changed, 256 insertions(+))
Open in Cloud Shell: Diff ( 8 files changed, 290 insertions(+))

[modular-magician]

Tests analytics

Total tests: 79
Passed tests: 75
Skipped tests: 2
Affected tests: 2

Click here to see the affected service packages

• alloydb

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

• TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample
• TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample

Get to know how VCR tests work

[modular-magician]

Tests analytics

Total tests: 79
Passed tests: 75
Skipped tests: 2
Affected tests: 2

Click here to see the affected service packages

• alloydb

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

• TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample
• TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample

Get to know how VCR tests work

[modular-magician]

🔴 Tests failed during RECORDING mode:
TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample [Error message] [Debug log]
TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample [Error message] [Debug log]

🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR.

View the build log or the debug log for each test

[modular-magician]

🔴 Tests failed during RECORDING mode:
TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample [Error message] [Debug log]
TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample [Error message] [Debug log]

🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR.

View the build log or the debug log for each test

[slevenick]

Looks like the tests aren't being generated with all the right values.

What's the goal here, to show before and after for updating the Postgres version? Is that a difficult upgrade path?

[modular-magician]

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.

google provider: Diff ( 2 files changed, 256 insertions(+))
google-beta provider: Diff ( 2 files changed, 256 insertions(+))
Open in Cloud Shell: Diff ( 8 files changed, 290 insertions(+))

[modular-magician]

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.

google provider: Diff ( 2 files changed, 256 insertions(+))
google-beta provider: Diff ( 2 files changed, 256 insertions(+))
Open in Cloud Shell: Diff ( 8 files changed, 290 insertions(+))

[modular-magician]

Tests analytics

Total tests: 79
Passed tests: 75
Skipped tests: 2
Affected tests: 2

Click here to see the affected service packages

• alloydb

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

• TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample
• TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample

Get to know how VCR tests work

[modular-magician]

Tests analytics

Total tests: 79
Passed tests: 75
Skipped tests: 2
Affected tests: 2

Click here to see the affected service packages

• alloydb

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

• TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample
• TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample

Get to know how VCR tests work

[modular-magician]

🟢 Tests passed during RECORDING mode:
TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample [Debug log]
TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.

---

🟢 All tests passed!

View the build log or the debug log for each test

[modular-magician]

🟢 Tests passed during RECORDING mode:
TestAccAlloydbCluster_alloydbClusterAfterUpgradeExample [Debug log]
TestAccAlloydbCluster_alloydbClusterBeforeUpgradeExample [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.

---

🟢 All tests passed!

View the build log or the debug log for each test

[GauravJain21]

Looks like the tests aren't being generated with all the right values.

What's the goal here, to show before and after for updating the Postgres version? Is that a difficult upgrade path?

Fixed the issue. It's a trivial CUJ but it's mandatory to launch this feature in GA.