Skip to content
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

Configurations List Api is broken? #302

Closed
arsunda opened this issue Apr 16, 2018 · 5 comments
Closed

Configurations List Api is broken? #302

arsunda opened this issue Apr 16, 2018 · 5 comments
Assignees
Labels
content Issue with content on docs.microsoft.com transferred Issue was transferred somewhere else.

Comments

@arsunda
Copy link

arsunda commented Apr 16, 2018

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???

@Powerhelmsman Powerhelmsman added triaged content Issue with content on docs.microsoft.com labels Apr 16, 2018
@Powerhelmsman
Copy link
Collaborator

@erickson-doug Can you take a look at this issue?

@Powerhelmsman
Copy link
Collaborator

@erickson-doug Any update?

@Powerhelmsman
Copy link
Collaborator

Sent a email to @erickson-doug to follow up

@Powerhelmsman
Copy link
Collaborator

@wnjenkin @elbatk Can you help assign to the right person?

@Powerhelmsman
Copy link
Collaborator

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issue with content on docs.microsoft.com transferred Issue was transferred somewhere else.
Projects
None yet
Development

No branches or pull requests

3 participants