-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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_storage_object_access_control does not encode path properly #9457
google_storage_object_access_control does not encode path properly #9457
Comments
@terorie example
|
@terorie talked to my colleague, its indeed bug on our end. We will work on it. |
@venkykuberan Thanks! This bug might affect more resources by the way. |
Hello All, having this same issue! |
It looks like google_storage_object_acl is handwritten & uses a client wrapper that presumably handles this conversion internally. |
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. |
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
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
The request should have succeeded.
The POST request to create the ObjectAccessControl resource should have escaped the path according to API Reference.
e.g.
POST /storage/v1/b/my-bucket/o/a%2fb%2fc/acl?alt=json
Actual Behavior
terraform-provider-google did not escape the path properly and made a POST request against
POST /storage/v1/b/my-bucket/o/a/b/c/acl?alt=json
, which does not map to any API endpoint.Steps to Reproduce
/
in its nameReferences
google_storage_*
resources don't encode object names properly #2895The text was updated successfully, but these errors were encountered: