Add tags field to Alloydb Backup for TagsR2401

[SamanthaMathews]

Add tags field to backup resource to allow setting tags on backup resources at creation time.
b/337048391
Release Note Template for Downstream PRs (will be copied)

alloydb: added `tags` field to `alloydb_backup` to allow setting tags for backups at creation time

[google-cla]

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.

[github-actions]

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

@ScottSuarez, 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, 113 insertions(+), 2 deletions(-))
google-beta provider: Diff ( 4 files changed, 113 insertions(+), 2 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 17 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_alloydb_backup (10 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_alloydb_backup" "primary" {
  tags = # value needed
}

[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:

• TestAccAlloydbBackup_tags
  $\textcolor{red}{\textsf{Errors occurred during REPLAYING mode. Please fix them to complete your PR.}}$

View the build log

[ScottSuarez]

Hi Samantha! Thanks for contributing, three things:

1. The code is failing to compile. Here is the error from the logs

# github.com/hashicorp/terraform-provider-google-beta/google-beta/services/alloydb
google-beta/services/alloydb/resource_alloydb_backup_test.go:326:2: expected declaration, found '}'

2. I don't see these fields documented on the API docs. Is that correct?

https://cloud.google.com/alloydb/docs/reference/rest/v1/projects.locations.backups

3. I don't appear to have access to the bug linked in the Pull Request - b/337048391

[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, 114 insertions(+), 2 deletions(-))
google-beta provider: Diff ( 4 files changed, 114 insertions(+), 2 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 17 insertions(+))

[modular-magician]

Tests analytics

Total tests: 74
Passed tests: 69
Skipped tests: 4
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

• TestAccAlloydbBackup_tags

Get to know how VCR tests work

[modular-magician]

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

$\textcolor{red}{\textsf{Errors occurred during RECORDING mode. Please fix them to complete your PR.}}$

View the build log or the debug log for each test

[c2thorn]

Discussing with @SamanthaMathews offline about this PR and the go rewrite migration