Open vladris opened 3 years ago
kusto
FWIW I reported a similar issue here: https://github.com/Azure/azure-cli/issues/13330
In that case, I believe the set of values allowed by the client was different than the set of values accepted by the server. I wonder if something similar is happening here, maybe slight difference in naming between UnrestrictedViewers and whatever the server expects.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @radennis.
So any thoughts on this?
Adding @ilayrn and @orhasban
Hi @vladris it is indeed bug in our clients, the role name is not supported in the server side. We will fix this issue, and future clients will have the right property name.
In the meanwhile, would you like us add the role to your database manually?
No, that's OK. Thanks for offering. I know how to add roles manually, was just looking at Azure CLI automation so I'll wait for the fix.
OK. Thanks for reporting this bug.
Any idea when this will be fixed?
We are planning to release new client (with the fix) around mid March. I'll update the thread once the new client is released.
Kusto
I'm trying to use the
az kusto database-principal-assignment
command to grant UnrestrictedViewers access but I get the following error:(BadRequest) Database principal role is invalid. Please provide valid database principal role (Admin, Viewer, User, etc.).
.Here is the full command for context:
Running
az kusto database-principal-assignment create -h
shows UnrestrictedViewers as one of the allowed values for role, but looks like the server rejects it.