Store Project variables

[LecrisUT]

It would be useful to allow to store some variables and/or secrets in the packit service/dashboard. This requires quite a lot of implementation so we could break it down in a few stages:

• Store public variables associated with project and have a substitution mechanism (jinja or plain bash?)
• Set and get variables via the CLI using the fas token (or forge tokens, but that might be too complicated for user)
• Add user authentication to dashboard.packit.dev and allow them to set/get variables
• Handle secret variables as well. These could be encrypted using the forge secret, depends a lot on the available APIs, have it symmetric or assymetric? Probably the previous step can narrow down a design

An example usage for this would be in packit#1902.

[lbarcziova]

We have met with Cristian and explained that as for the user authentication and handling secrets via dashboard, we do not want to implement this in any near future, taking our priorities into consideration (we did research on the authenticated dashboard in the past, and the outcome was that the implementation would be quite extensive).

Keeping this issue open to track the storing of the public variables, but this is currently low-prio for us.

[majamassarini]

@LecrisUT is this something still relevant for you?