feat(backupdr): introducing associations attached with csql instances

[kushallunkad-google]

Description

Fixes #<b/454546432>

Note: If you are not associated with Google, open an issue for discussion before submitting a pull request.

Checklist

Readiness

• Yes, merge this PR after it is approved
• No, don't merge this PR after it is approved

Style

• My sample follows the rules described for Terraform in the Effective Samples style guide
• My sample follows the other requirements and best practices in the Contributing
  guide

Testing

• I have performed tests described in the Contributing guide:

  • Tests pass: terraform apply
  • Lint pass: terraform fmt check

Intended location

• Yes, this sample will be (or already is) included on cloud.google.com
  Location(s):https://cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-plan-create#create and https://cloud.google.com/backup-disaster-recovery/docs/cloud-console/sql/csql-backup#configure_a_scheduled_backup

• No, this sample won't be included on cloud.google.com
  Reason:

API enablement

• If the sample needs an API enabled to pass testing, I have added the service to the Test setup file

Review

• If this sample adds a new directory, I have added codeowners to the CODEOWNERS file

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• backupdr/backup_plan_association/main.tf:205, tag backupdr_create_backupplanassociation_csql

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[glasnt]

This should be created in a separate PR. It's unrelated to this feature

[kushallunkad-google]

Actually both the changes were part of the same bug that is why created a single pull request.

[kushallunkad-google]

I am sorry but we would need to hold this PR for a few days as there is some issue which is being resolved , thanks!

[glasnt]

The tests are failing with deletion step blocking:

Error waiting for Deleting BackupPlanAssociation: Error code 9, message: There is already a pending blocking operation for instance: ci-tf-samples-1-lszrmlcq:instance-test

I'm not sure if this is an issue with the provider, or something else that's affecting resource cleanup.

[kushallunkad-google]

The tests are failing with deletion step blocking:

Error waiting for Deleting BackupPlanAssociation: Error code 9, message: There is already a pending blocking operation for instance: ci-tf-samples-1-lszrmlcq:instance-test

I'm not sure if this is an issue with the provider, or something else that's affecting resource cleanup.

This is a timing issue in the test workflow, not a defect in the service API or the Terraform provider. The resource cleanup is happening too quickly, before the service has completed its mandatory initial operation(As soon as backup plan association is created it triggers a backup -> which is a pending operation).
This should not be a problem in production environments, as resources typically exist long enough for initial operations to complete.