How to create a Custom OSS provider

[fabrice.mejean]

Hi,

I'm intrusted on how to create a Custom OSS provider. On the documentation you don't explain what is the expected format, if it's an API ...

Could you explain how to implement it correctly please ?

Regards,

Fabrice MÉJEAN

[stevedennis]

Hi @fabrice-mejean ,

I'm not sure what you mean by "Custom OSS provider", can you clarify?

Thanks,
Steve

[fabrice.mejean]

Custom Metadata Provider : https://docs.inedo.com/docs/proget/sca/policies?utm_source=proget&utm_medium=product&utm_campaign=proget24_0#oss-metadata-updating-caching

[dean-houston]

Hi @fabrice-mejean ,

Oh I see; that's basically just an alternative URL to query, instead of (or in addition to) official public repositories.

For example, the OSS Metadata Provider for npm is https://registry.npmjs.org. A Custom Provider is one with an alternative URL. Maybe a vendor site, or a differente repository that uses the same APIs?

As the docs mentioned, we have no idea why anyone would want to do that. But it's technically possible.

Thanks,
Steve

[fabrice.mejean]

Oh ok, I was thinking that we could create a private metadata provider if we want deprecate our own packages without doing it on each feeds. So it will not help me. Thanks