Azure-devops-docs: Orginazation Scoped Feeds

[RichardMeadowsTC]

Where is the documentation for creating an organization scoped feed? I need a new feed that is Organization-scoped.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3db27124-fabe-5ab3-0f2e-e866cabff257
• Version Independent ID: c64aad85-16eb-919a-aff1-34f350065019
• Content: What are feeds? - Azure Artifacts
• Content Source: docs/artifacts/concepts/feeds.md
• Product: devops
• Technology: devops-artifacts
• GitHub Login: @chasewilson
• Microsoft Alias: phwilson

[randomITperson]

I am looking for the same as well. Existing feeds are switched to organizational scope and we have to create more but we can only create project scoped feeds now. Any help is appreciated.

[msebolt]

@RichardMeadowsTC Thank you for the question, assigning this to the author for review.

Please refer to the open issue here for feedback and updates from the product team.

Details on using the API can be found here.

[cdietschrun]

What's the status here of the documentation? It's not clear at all to me how to make something organization scoped.

[cdietschrun]

It looks like we're expected to use the REST API to switch to organization scoped. This does not seem sufficient to me, why was this removed from the UI?

[kieronlanning]

@msebolt Our release pipelines are breaking because the url the DotNetCLI task is generating is based on a organisational feed, not a project one.

Can you update the docs for fix both the creation of organisation feeds and for the DotNetCLI YAML task, in particular the push command.

[brunomartinspro]

Any changes on this?

[RichardMeadowsTC]

No change yet. Microsoft thinks people don’t need Org scoped feeds still. Last time I checked, the documentation for using REST api to create a feed makes no mention of Org scoped feed. Possible to do. But you have to know about not including the Project name in REST url.

Richard Meadows

From: Bruno [e-mail]
Sent: Thursday, April 30, 2020 6:55 AM
To: MicrosoftDocs/[e-mail]
Cc: Richard [e-mail]; [e-mail]
Subject: Re: [MicrosoftDocs/azure-devops-docs] Orginazation Scoped Feeds (#6715)

Any changes on this?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-devops-docs/issues/6715#issuecomment-621868259, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI5HOOCXEHNOZPRZIESE773RPF7NHANCNFSM4J4CTEQQ.

[ramiMSFT]

@RichardMeadowsTC Thank you for your feedback. Creating a new organization-scoped feeds through the UI is not supported.

• All new feeds are recommended to be project-scoped. Creating a new feed through the create feed panel will create a project-scoped feed.

• You can use the Create Feed API to manually create a new organization-scoped feed. You will have to set the default permissions for the new feed manually either by using the Feed Permission API or the Artifacts feed settings. Creating new organization-scoped feeds is not recommended.

A "Suggest a feature" ticket has been submitted for: organisation-scoped-feeds

You can up vote to increase the priority of this feature. Thank you

[RichardMeadowsTC]

My security guy is making me use project scoped artifact feed. Apparently, the security really isn’t there. Will see about that. The build account is supposed to have access to feeds from all the projects. Like what I have.

Richard Meadows

From: Bruno [e-mail]
Sent: Thursday, April 30, 2020 8:16 AM
To: MicrosoftDocs/[e-mail]
Cc: Richard [e-mail]; [e-mail]
Subject: Re: [MicrosoftDocs/azure-devops-docs] Orginazation Scoped Feeds (#6715)

@ramiMSFThttps://github.com/ramiMSFT can someone then explain to me how are we going to share microservices artifacts if sharing artifacts between projects is not recommended?

Example:

Architecture Project

Project A
Repository A
Repository B

Project B
Repository C uses Architecture Artifacts
Repository D uses ProjectA Artifacts

Furthermore there is the issue of the package replacement settings not having a “allow package replacement”.

So this was closed because there is nothing we can do to support microservices?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-devops-docs/issues/6715#issuecomment-621919551, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI5HOOAYMRT2KHAZ2IZSTQDRPGI6PANCNFSM4J4CTEQQ.

[brunomartinspro]

At this point I’m just trying to understand why the concept of feeds of Microsoft is so different from the rest of the solutions out there in the world.

My first issue was with package replacement - why would anyone force teams to increase the versions of packages? Couldn’t this be a setting? What if something goes wrong in a build and we need to replace it with the same version to send it to the client? Should we say to the client “Hi, unfortunately we ran into an issue and we won’t be releasing 1.0.0, we will be releasing 1.0.1” even though the 1.0.0 version never went to the customer.

If the API allows the creation of Organization feeds, why would it not be in the UI? Since the frontend runs JavaScript couldn’t it call the API with an internal token and configure the permissions in the UI as well?

So someone works in a company with 3000 projects and wants to share a feed with 2 projects (or the 3000 if it’s an architecture project) - why would it be a security issue to give two clicks in the UI to select a project to give access? Why would it be safer to only have access to a project?