Describe what you need us to do: As RelEng it is sometimes useful to able to process the fedora scm requests. I am not going to process them all, but sometimes people come to releng asking with some special requests, for example: https://pagure.io/releng/fedora-scm-requests/issue/7127
When do you need this? (YYYY/MM/DD) No urgency, whenever possible
If we cannot complete your request, what is the impact? When something like this happens, I have to find someone who can handle these requests and afaik there are only couple of people around and if I cannot be able to reach anyone of them they the fedora scm request has to wait until someone is available.
IRC chat with @pingou
[15:23:15] <pingout> sure, mind opening an infra ticket for this? ... [15:29:24] <pingout> which tokens do you have/need the pagure.io or the src.fp.o one? [15:30:57] <mboddu> I think src.fp.o as the docs didn't specify much https://pagure.io/fedscm-admin/ [15:32:09] <mboddu> whatever the pagure-admin tool generates (I guess) [15:34:46] <pingout> it uses both [15:34:58] <pingout> one for pagure.io to comment/close the tickets [15:35:07] <pingout> one for src.fp.o to create the repo
You should be able to generate the token for pagure.io yourself in the settings of the project. You'll need ACLs for commenting and updating/closing the tickets (iirc, you don't need more).
I have generated the API token for src.fp.o, it is available in your user's settings on src.fp.o. I also extended the expiration date so it expires at the end of 2018 as does the token used by tibbs and limb (so we'll get the renew them all at the same time).
Let us know if you need anything else :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue priority set to: None (was: Needs Review)
Login to comment on this ticket.