Mark DiskEncryptionKey.rawKey as sensitive for Terraform

[Shegox]

This PR marks the raw disk encryption key in Terraform as sensitive and therefore doesn't output it to the console log.

Inspired by:

magic-modules/products/compute/terraform.yaml

Lines 1445 to 1452 in b67500f

	snapshotEncryptionKey.rawKey: !ruby/object:Overrides::Terraform::PropertyOverride
	# This is _correct_, but we don't support ignore_read on nested fields
	# so we use a custom_flatten for now.
	# https://github.com/GoogleCloudPlatform/magic-modules/issues/1019
	ignore_read: true
	sensitive: true
	required: true
	custom_flatten: templates/terraform/custom_flatten/compute_snapshot_snapshot_encryption_raw_key.go.erb

I'm not 100% sure if changes to at other points are required or not.

Changes need to end in the end in the terraform-provider-google resource_compute_disk.

Release Note Template for Downstream PRs (will be copied)

compute: `google_compute_disk` `disk_encryption_key.raw_key` is now sensitive

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[modular-magician]

Hello! I am a robot who works on Magic Modules PRs.

I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. They will authorize it to run through our CI pipeline, which will generate downstream PRs.

Thanks for your contribution! A human will be with you soon.

@emilymye, please review this PR or find an appropriate assignee.

[emilymye]

this needs to be lowercase camel, but once that's done it should be ok!

[Shegox]

Thanks for the quick look and good catch, fixed it in 219cfe6.

CCLA should be signed soonish as well when I get added to the group from our team.

[emilymye]

@Shegox let me know when you've gotten the CLA fixed or comment/edit PR and the googlebot should fix it? i can also override

[Shegox]

@emilymye I'm still waiting on the internal process to get added to our corporate CLA group. I would like to give it another day and otherwise just do it as a personal contribution otherwise.

[Shegox]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[modular-magician]

Hello! I am a robot who works on Magic Modules PRs.

I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. They will authorize it to run through our CI pipeline, which will generate downstream PRs.

Thanks for your contribution! A human will be with you soon.

@danawillow, please review this PR or find an appropriate assignee.

[danawillow]

Thanks @modular-magician, but looks like @emilymye has this one covered :)

[modular-magician]

Hi! I'm the modular magician, I work on Magic Modules.
I see that this PR has already had some downstream PRs generated. Any open downstreams are already updated to your most recent commit, 219cfe6.

Pull request statuses

No diff detected in terraform-google-conversion.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google-beta#1445
depends: hashicorp/terraform-provider-google#5009

[modular-magician]

Hi! I'm the modular magician, I work on Magic Modules.
I see that this PR has already had some downstream PRs generated. Any open downstreams are already updated to your most recent commit, ce16f36.

Pull request statuses

No diff detected in terraform-google-conversion.
No diff detected in terraform-provider-google.
No diff detected in Ansible.
No diff detected in Inspec.

New Pull Requests

I built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google-beta#1452

[emilymye]

@Shegox I moved this over to #2766 - I merged the downstreams but didn't realize merge would fail on this PR because it's from a master branch and our tool currently doesn't handle it very well. It'll still show up as your commit without extra work on your end - just wanted to let you know why you're getting tagged in an identical PR

[emilymye]

merged via #2766, closing