Closed SebastianSchuetze closed 1 year ago
Hi @SebastianSchuetze
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)
Get-VSTeamFeed
, add a new property Scope
to the returned objects with 2 possible values: Project or OrganizationI 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. 😃
Or, at least, we add an additional example:
Get-VSTeamFeed | where url -Match "https://feeds.dev.azure.com/$organziation/_apis/Packaging"
This command returns only the package feeds at organization scope
@mnieto can you propose this as a feature? I think putting in a closed PR is the wrong place. :)
just copy&paste
PR Summary
Added the possibility to create, get and delete artifacts feeds scoped to projects
fixes #379
PR Checklist