feat(bigquery): Add example for creating a table with tag attached

[pratikmore0290]

Description

Fixes #353964666

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/bigquery/docs/tags#attach_tags_when_you_create_a_new_table

• 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.

• bigquery/bigquery_create_table_attach_tag/main.tf:17, tag bigquery_create_table_attach_tag

---

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

[pratikmore0290]

/gcbrun

[glasnt]

/gcbrun

[glasnt]

/gcbrun

[glasnt]

Terraform destroy is failing due to dependency issues:

Error: Error waiting for Deleting TagValue: Error code 9, message: Cannot delete tag value, 
tagValues/[value], because it is still attached to resources in 'us' region. To delete this tag value, 
remove all holds and then remove it from all resources. At least one binding was found to 
an active or deleted resource in the 'us' region.

I need to investigate more, as this part concerns me:

At least one binding was found to an active or deleted resource in the 'us' region.

This error did not occur in #733

[glasnt]

/gcbrun

[glasnt]

Logged upstream issue

[priyanshsaxena]

The resource is adding tags at creation. Since Terraform can deduce the implicit dependency of the table-resource on tag-value-resource because of the resource_tags field, the creation-order should be value-then-table. Terraform documentation mentions that both implicit and explicit dependencies should affect the order of creation and destruction.

One way to explicitly mark the dependency is to use the depends_on meta-field. Please try to run the graph command before and after adding the explicit dependency to see if changes anything.

terraform graph -type=plan | dot -Tpng >graph.png

[glasnt]

The resource is adding tags at creation. Since Terraform can deduce the implicit dependency of the table-resource on tag-value-resource because of the resource_tags field, the creation-order should be value-then-table. Terraform documentation mentions that both implicit and explicit dependencies should affect the order of creation and destruction.

One way to explicitly mark the dependency is to use the depends_on meta-field. Please try to run the graph command before and after adding the explicit dependency to see if changes anything.

terraform graph -type=plan | dot -Tpng >graph.png

I've tried adding depends_on in multiple forms in local testing, but it didn't work, hence the upstream report.

[glasnt]

To unblock this for now, we can add test.yaml to remove testing this sample.

[glasnt]

/gcbrun

[pratikmore0290]

/gcbrun

[glasnt]

/gcbrun