pagure

#3948 Ability to use (Webhook sign material/notitifcation url(s)/API key) for a group of projects
Closed: Fixed by fbo. Opened by fbo.

Closed: Fixed
Reopen Issue

Use case is to use the same events hook, sign material, API token for multiple repositories.

For instance if I want to receive events, run jobs as a third party system (CI), then report on pagure for multiple projects then I need one triplet (event hook url, event hook sign token, API token) by project. It is manageable for a low amount of project (< 10) but unpractical for more (ex: cross repo gating on packaging repos mean usually > 100 repos to handle).

An idea would be to attach (api key, notification url, webhook sign material) to a group of projects. Then each project in that group inherit of that triplet.

For trusted services we have ways to provide project-less API token (ie: api token valid for all and every projects).

This RFE is interesting but will require some changes on how we link tokens to projects and some UI/API work.

It's not a priority for me atm, but I'll review a PR if someone wants to work on it :)

Metadata Update from @pingou:
- Issue tagged with: RFE

Hi, interesting, how can I get that project-less API token ?

A simpler approach I propose is:
https://pagure.io/pagure/pull-request/4221
https://pagure.io/pagure/pull-request/4223

Hi, interesting, how can I get that project-less API token ?

By asking your friendly pagure admin :)

I think we can close that RFE. The I have implemented my use cases via 4221 and 4223.

Metadata Update from @fbo:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

RFE

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.