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
Be as descriptive as you can with your idea/bug report/question/suggestion.
Issue Details
When using the api specified here , the list api works fine. However, when specifying any scope parameters using the format specified in the page, the value returned is always an empty list { "count": 0, "value": [] }
When i have no scope specified, I get a list of policies which have this field
eg: "scope": [ { "refName": "refs/heads/master", "matchKind": "Exact", "repositoryId": "{repo-id}" } ]
Using the refName or the repository id with wildcards, or using them both to specify the scope always returns the empty value as above. Using the policy parameter works fine
Has anything changes with regards to how this api is documents/set up???
The text was updated successfully, but these errors were encountered:
@arsunda Your issue is transferred to vsts-rest-api team. They will help you there. I will close as transferred. If you have other question related to this issue, we can reopen it and continue discussion.
Idea Title
Be as descriptive as you can with your idea/bug report/question/suggestion.
Issue Details
When using the api specified here , the list api works fine. However, when specifying any scope parameters using the format specified in the page, the value returned is always an empty list
{ "count": 0, "value": [] }
When i have no scope specified, I get a list of policies which have this field
eg:
"scope": [ { "refName": "refs/heads/master", "matchKind": "Exact", "repositoryId": "{repo-id}" } ]
Using the refName or the repository id with wildcards, or using them both to specify the scope always returns the empty value as above. Using the policy parameter works fine
Has anything changes with regards to how this api is documents/set up???
The text was updated successfully, but these errors were encountered: