projects.setIamPolicy
API call does not modify auditConfigs
but modifies bindings
#3506
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is this a client library issue or a product issue?
This is the client library for . We will only be able to assist with issues that pertain to the behaviors of this library. If the issue you're experiencing is due to the behavior of the product itself, please visit the Support page to reach the most relevant engineers.
Did someone already solve this?
Please create an issue in the support console to ensure a timely response.
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
googleapis
version: 118.0.0Steps to reproduce
auditConfigs
andbindings
. Make sure we addexemptedMembers
to the config with service asallServices
bindings
will be updated but the changes inauditConfigs
will not be updatedWhen we try to update
auditConfigs
using theprojects.setIamPolicy
API any change is not reflected however when using the console or the CLI (gcloud projects set-iam-policy parker-aac policy.json
where we have a file policy.json with the updated request body) we are able to update it especially when changing theexemptedMembers
parameter.We do have a documentation supporting this > https://cloud.google.com/resource-manager/reference/rest/v1/projects/setIamPolicy
Since we are able to update it using the CLI or from the console we should be able to do with the API as well.
Also the API is able to update the
bindings
then why not theauditConfigs
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: