-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
google_os_config_patch_deployment windows_update staza should allow classifications AND excludes #13158
google_os_config_patch_deployment windows_update staza should allow classifications AND excludes #13158
Comments
@ChrisAndrews why do you think they should be allowed? Can you share the related documents? Can you also share your config? |
@ChrisAndrews can you share your code and the debug log? |
Here's the complete resource code; I put the log of the error above: instance_filter { patch_config {
} recurring_schedule {
} |
It appears the API has updated its behavior for |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Affected Resource(s)
When creating a patch_config for windows servers the windows_update stanza, the terraform config does not match the functionality of the GCP UI.
In the GCP console you can specify classifications, but exclude specific KB's.
I've created my Terraform config like so:
` patch_config {
reboot_config = "NEVER"
However the terraform plan fails:
Expected outcome:
This stanza should allow a combination of 'classifications' and/or 'excludes', or 'exclusive_patches', but NOT 'exclusive_patches' and either 'classifications' or 'excludes'.
b/300238108
The text was updated successfully, but these errors were encountered: