docs: Update GMK resource examples now that Clusters and Topic resources are GA

[jessdejong]

Description

GMK Clusters and Topics are getting promoted to GA after the submission of GoogleCloudPlatform/magic-modules#12264. We need to update our public documentation to use our GA resources instead of the google-beta ones. Issue: https://b.corp.google.com/issues/377724373

Checklist

Readiness

• Please approve this PR, but wait submit after Promoting Managed Kafka Cluster and Topic resources to GA GoogleCloudPlatform/magic-modules#12264 is submitted.

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/managed-service-for-apache-kafka/docs/create-cluster#create

• 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

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[jessdejong]

This may need (but I might not be able to successfully trigger this).

/gcbrun

[johndee7310]

LGTM! Ship it for GA

[glasnt]

Error: Error creating Cluster: googleapi: Error 404: Resource "projects/261919062524/regions/us-central1/subnetworks/default" was not found

This isn't being specifically created in the sample, but I'm not sure if it should exist in the project. You could either use the resource to create the subnetwork specifically, or use the data resource to pull the existing information (https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/compute_subnetwork).

I'll /gcbrun it again to confirm it's not a temporary issue (previous issues were "internal errors", this is something specific)

[jessdejong]

"default" subnetworks should exist in the project as long as the compute API is enabled. But I checked and the project with project number "261919062524" is being deleted or already has been deleted.

[jessdejong]

I'm confused, why would the CI tests be on a deleted project? Or maybe the project was deleted after the tests were run, which is more likely. I'll look into using the subnet terraform resource in my sample.

[snippet-bot]

Here is the summary of changes.

You are about to add 2 region tags.

• managedkafka/managedkafka_create_cluster/main.tf:37, tag managedkafka_subnetwork
• managedkafka/managedkafka_create_topic/main.tf:35, tag managedkafka_subnetwork

---

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

[jessdejong]

The tests should be running, now that I've updated the Cluster and Topic samples to make their own subnets with the google_compute_subnetwork resource.

[jessdejong]

Please let me know if there's anything else that I can do!

[jessdejong]

Hi, I'm not able to see what went wrong in the latest CI test. Could someone give me some insights so I can try and fix the errors?

[jessdejong]

@glasnt My team would like to include the project field on the google_managed_kafka_cluster and google_managed_kafka_topic resource samples. I have already committed these changes, but given that this might not be standard practice (@apeabody), I would like you to take a look at this again if possible. We decided to include the project field in b/377892703.