You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
It appears there is a camelcase issue here. Getting requireScreenLock instead of the google api field requireScreenlock (google is inconsistent in this one case)
The text was updated successfully, but these errors were encountered:
I can repro this issue. Above code works fine if I set require_screen_lock =false. But once I set it to require_screen_lock=true, it generates above error.
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.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
May 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.12.24
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
it creates a policy with requireScreenLock
Actual Behavior
Error: Error updating AccessLevel "accessPolicies/XXXXX/accessLevels/bug": googleapi: Error 400: Invalid JSON payload received. Unknown name "requireScreenLock" at 'access_level.basic.conditions[0].device_policy': Cannot find field.
Steps to Reproduce
terraform apply
Important Factoids
References
https://cloud.google.com/access-context-manager/docs/reference/rest/v1beta/accessPolicies.accessLevels?hl=en#DevicePolicy
https://github.com/terraform-providers/terraform-provider-google/blob/master/google/resource_access_context_manager_access_level.go#L544
It appears there is a camelcase issue here. Getting
requireScreenLock
instead of the google api fieldrequireScreenlock
(google is inconsistent in this one case)The text was updated successfully, but these errors were encountered: