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
The ResourceLink portion of the string is the identity property of the resource that the request is directed at. ResourceLink must maintain its case for the id of the resource. Example, for a collection it will look like: "dbs/MyDatabase/colls/MyCollection"
[5.1] Version of PowerShell you're using
[Console host and VS Code] PowerShell host you're using (eg. Console Host, ISE, Visual Studio)
[Win10 x64] Operating system you're running
[2.0.7.342] Version of CosmosDB you're using (use Get-Module -Name CosmosDB)
The text was updated successfully, but these errors were encountered:
I'm having the same problem. I was getting 401 errors when I tried to add a new stored procedure to a collection with a camel cased name. I made a separate test collection with all lowercase letters for the ID and the script Posted the same stored procedures to that collection just fine.
Running PowerShell 6.0.2 on a Windows 10 x64 machine in the PowerShell console. I'm using CosmosDB 2.0.7.288, and also just for fun I got the same behavior to happen on a VSTS release definition with Azure PowerShell.
Wow - not sure how I messed that up - but thanks for catching this, raising this issue and the PR. Really shows I need to get the integration tests story completed. I'll get this reviewed and out this evening for you. Thanks @MWL88 and @ThePeavstenator.
Function New-CosmosDbAuthorizationToken incorrectly converts the ResourceLink (ResourceId variable) to lowercase here.
The MS documentation states
Get-Module -Name CosmosDB
)The text was updated successfully, but these errors were encountered: