-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Compute disk write only attributes #14145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Compute disk write only attributes #14145
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_disk" "primary" {
description = # value needed
disk_encryption_key {
rsa_encrypted_key_wo = # value needed
rsa_encrypted_key_wo_version = # value needed
}
interface = # value needed
source_image_encryption_key {
kms_key_self_link = # value needed
kms_key_service_account = # value needed
raw_key = # value needed
}
source_snapshot_encryption_key {
kms_key_self_link = # value needed
kms_key_service_account = # value needed
raw_key = # value needed
}
}
Missing doc report (experimental)The following resources have fields missing in documents.
|
Tests analyticsTotal tests: 1213 Click here to see the affected service packages
Found 9 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🟢 No issues found for passed tests after REPLAYING rerun. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. Missing test reportYour PR includes resource fields which are not covered by any test. Resource: resource "google_compute_disk" "primary" {
description = # value needed
disk_encryption_key {
rsa_encrypted_key_wo = # value needed
rsa_encrypted_key_wo_version = # value needed
}
interface = # value needed
source_image_encryption_key {
kms_key_self_link = # value needed
kms_key_service_account = # value needed
raw_key = # value needed
}
source_snapshot_encryption_key {
kms_key_self_link = # value needed
kms_key_service_account = # value needed
raw_key = # value needed
}
}
Missing doc report (experimental)The following resources have fields missing in documents.
|
Tests analyticsTotal tests: 1213 Click here to see the affected service packages
Found 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
🟢 Tests passed during RECORDING mode: 🟢 No issues found for passed tests after REPLAYING rerun. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
compute: added
raw_key_wo
,rsa_encrypted_key
andnew_keys_wo
fields inresource_google_compute_disk
resourcecompute: added
raw_key_woand
new_keys_wofields in
resource_google_region_compute_diskresource
And resolved the previous 404 error that arose due to adding these write only fields.
See Write release notes for guidance.