Adding in datasource for google_alloydb_cluster

[NA2047]

Adding in a data source for google_alloydb_cluster

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

`google_alloydb_cluster`

[github-actions]

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

@roaks3, 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 ( 4 files changed, 180 insertions(+))
google-beta provider: Diff ( 4 files changed, 410 insertions(+), 232 deletions(-))

Errors

google provider:

• The diff processor failed to build. This is usually due to the downstream provider failing to compile.

google-beta provider:

• The diff processor failed to build. This is usually due to the downstream provider failing to compile.

[modular-magician]

Tests analytics

Total tests: 0
Passed tests: 0
Skipped tests: 0
Affected tests: 0

Click here to see the affected service packages

• alloydb

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

View the build log

[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 ( 4 files changed, 164 insertions(+))
google-beta provider: Diff ( 4 files changed, 394 insertions(+), 232 deletions(-))

[modular-magician]

Tests analytics

Total tests: 0
Passed tests: 0
Skipped tests: 0
Affected tests: 0

Click here to see the affected service packages

• alloydb

#### Non-exercised tests

🔴 Tests were added that are skipped in VCR:

• TestAccAlloydbDatabaseClusterDatasourceConfig
  🔴 Errors occurred during REPLAYING mode. Please fix them to complete your PR.

View the build log

[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 ( 4 files changed, 164 insertions(+))
google-beta provider: Diff ( 4 files changed, 395 insertions(+), 233 deletions(-))

[modular-magician]

Tests analytics

Total tests: 77
Passed tests: 73
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

• TestAccAlloydbDatabaseClusterDatasourceConfig
• TestAccAlloydbDatabaseInstanceDatasourceConfig

Get to know how VCR tests work

[modular-magician]

🟢 Tests passed during RECORDING mode:
TestAccAlloydbDatabaseClusterDatasourceConfig [Debug log]
TestAccAlloydbDatabaseInstanceDatasourceConfig [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

[roaks3]

Mostly LGTM, but I think the other datasources should be left in, and the filenames should be fixed

[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 ( 4 files changed, 154 insertions(+))
google-beta provider: Diff ( 4 files changed, 156 insertions(+), 2 deletions(-))

[modular-magician]

Tests analytics

Total tests: 77
Passed tests: 74
Skipped tests: 2
Affected tests: 1

Click here to see the affected service packages

• alloydb

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

• TestAccAlloydbDatabaseClusterDatasourceConfig

Get to know how VCR tests work

[modular-magician]

🟢 Tests passed during RECORDING mode:
TestAccAlloydbDatabaseClusterDatasourceConfig [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]

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 ( 4 files changed, 154 insertions(+))
google-beta provider: Diff ( 4 files changed, 154 insertions(+))

[modular-magician]

Tests analytics

Total tests: 77
Passed tests: 75
Skipped tests: 2
Affected tests: 0

Click here to see the affected service packages

• alloydb

🟢 All tests passed!

View the build log