feat(GKE): Add secondary boot disk sample for preloaded data

[aston-github]

Description

Fixes #

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/kubernetes-engine/docs/how-to/data-container-image-preloading

• 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 3 region tags.

• gke/standard/zonal/secondary-boot-disk/main.tf:17, tag gke_standard_zonal_secondary_boot_disk_cluster
• gke/standard/zonal/secondary-boot-disk/main.tf:30, tag gke_standard_zonal_secondary_boot_disk_container
• gke/standard/zonal/secondary-boot-disk/main.tf:51, tag gke_standard_zonal_secondary_boot_disk_data

You are about to delete 1 region tag.

• gke/standard/zonal/secondary-boot-disk/main.tf:17, tag gke_standard_zonal_secondary_boot_disk

---

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

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

[aston-github]

/gcbrun

[apeabody]

/gcbrun

[apeabody]

Thanks @aston-github!

The "renamed" tag was brand new: #675

[aston-github]

VCR test was failing due to a panic during type assertion in expandNodeConfig. I submitted changes in magic-modules to gracefully handle the config type assertion in hashicorp/terraform-provider-google#18323 . I added a near identical test case to the acceptance test in magic-modules, which passed. Machine type is the only difference.

[apeabody]

Unclear why the test is failing, seems like ${_BASE_BRANCH} isn't being populated for some reason?

@aston-github - maybe try amending your last commit? (or similar)

[apeabody]

/gcbrun

[apeabody]

OK - The CI test appears to be running correctly after the new commit.

[apeabody]

/gcbrun

[apeabody]

/gcbrun