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

Get-VSTeamFeed: distinguish between project and organization level scope feeds #487

Open
mnieto opened this issue Sep 10, 2022 · 1 comment
Assignees
Labels
feature request for new feature requests that do not just improve things

Comments

@mnieto
Copy link
Contributor

mnieto commented Sep 10, 2022

Background

Because the lack of a specific API for this, or because an unexpected behaviour of the current API , it is hard to distinguish between project scoped feeds and organization scoped ones.

Accordingly with the API documentation:

If the project parameter is present, gets all feeds in the given project. If omitted, gets all feeds in the organization.

But if we omit the project name, what we get is the complete list of feeds (project and organization scoped)

Proposal

Example

Get-VSTeamfeed

Name Description Id                                   Scope        ProjectId
---- ----------- --                                   -----        ---------
demo             f6ffc6ee-ea53-4612-8f5d-6f95b8738a2b Project      f6ffc6ee-ea53-4612-8f5d-6f95b8738a2b
global           f6ffc6ee-ea53-4612-8f5d-aaaa89542baa Organization

I know that this can be achieved with a script after calling Get-VSTeamFeed, but it could be nice to have it already implemented in the module. 😃

Solved Problem

There is no a direct way to list only organization scoped feeds

Additional info / code snippets?

Get-VSTeamFeed | where url -Match "https://feeds.dev.azure.com/$organziation/_apis/Packaging"

This command returns only the package feeds at organization scope

@mnieto mnieto added the feature request for new feature requests that do not just improve things label Sep 10, 2022
@SebastianSchuetze SebastianSchuetze self-assigned this Sep 10, 2022
@SebastianSchuetze
Copy link
Collaborator

SebastianSchuetze commented Sep 10, 2022

Started to work on this. Should be relatively easy to implement. I noticed the Azure CLI has the same scope. I will orientate on this implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request for new feature requests that do not just improve things
Projects
None yet
Development

No branches or pull requests

2 participants