You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming garm release, the github credential section is being removed from the config / migrated to the garm database. Github credentials and endpoints are then only managed via the garm-api. Therefore, the garm-operator needs to expose this as well. See PR #243
Key takeaways whilst interacting with garm-cli of current main branch:
[github] section in config.toml will be migrated if db table for credentials does not exist on first startup of garm
There can be multiple endpoints with the same URL => distinguisged by endpoint_name
For each endpoint, there can be multiple github credential entries
So the operator needs to be able to do the following operations:
What is the feature you would like to have?
With the upcoming garm release, the github credential section is being removed from the config / migrated to the garm database. Github credentials and endpoints are then only managed via the garm-api. Therefore, the garm-operator needs to expose this as well. See PR #243
Key takeaways whilst interacting with garm-cli of current main branch:
[github]
section inconfig.toml
will be migrated if db table for credentials does not exist on first startup of garmSo the operator needs to be able to do the following operations:
Anything else you would like to add?
No response
The text was updated successfully, but these errors were encountered: