The 'where to renew token part' has already an open issue:
https://pagure.io/pagure/issue/4510
For the src.fp.o case, we discussed about that here:
https://pagure.io/pagure/pull-request/4521
IMO, a solution that can fix both can be to add flask support to the croned .py that
produces the email and add a theme overwriting capability to that part. Default theme
would just add a url_for() link to the api renewing view and srcfpo theme would extend it
to add more specific info.
The issue is on my radar, but did not have time to reach there yet
On August 16, 2019 11:20:25 AM GMT+02:00, "Miro Hrončok"
<mhroncok(a)redhat.com> wrote:
Hey! I just got this e-mail.
Consider this an RFE to tell me where to renew the token.
For Fedora purposes, it would also be nice if it told me where to put
it to
continue packaging smoothly.
Thanks,
Your Pagure User.
PS, if you reply, please make sure I stay in the recipients.
-------- Forwarded Message --------
Subject: [Pagure] Pagure API key expiration date is near!
Date: Fri, 16 Aug 2019 00:00:10 +0000 (UTC)
From: pagure(a)pagure.io
To: mhroncok(a)redhat.com
Hi Miro Hrončok,
Your Pagure API key fedpkg.pagure will expire in 5 day(s).
Please get a new key for non-interrupted service.
Thanks,
Your Pagure Admin.
_______________________________________________
Pagure-devel mailing list -- pagure-devel(a)lists.pagure.io
To unsubscribe send an email to pagure-devel-leave(a)lists.pagure.io
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.pagure.io/archives/list/pagure-devel@lists.pagure.io
Julen Landa Alustiza <jlanda(a)fedoraproject.org>