Move URLs from default section of config to DB
This change moves the callback_url, metadata_url and webhooks_url from the config to the database. The goal is to move as much as possible from the config to the DB, in preparation for a potential refactor that will allow GARM to scale out. This would allow multiple nodes to share a single source of truth. Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
This commit is contained in:
parent
7ee235aeb0
commit
9748aa47af
22 changed files with 1067 additions and 177 deletions
45
testdata/config.toml
vendored
45
testdata/config.toml
vendored
|
|
@ -249,48 +249,3 @@ disable_jit_config = false
|
|||
# anything (bash, a binary, python, etc). See documentation in this repo on how to write an
|
||||
# external provider.
|
||||
provider_executable = "/etc/garm/providers.d/azure/garm-external-provider"
|
||||
|
||||
# This is a list of credentials that you can define as part of the repository
|
||||
# or organization definitions. They are not saved inside the database, as there
|
||||
# is no Vault integration (yet). This will change in the future.
|
||||
# Credentials defined here can be listed using the API. Obviously, only the name
|
||||
# and descriptions are returned.
|
||||
[[github]]
|
||||
name = "gabriel"
|
||||
description = "github token or user gabriel"
|
||||
# This is the type of authentication to use. It can be "pat" or "app"
|
||||
auth_type = "pat"
|
||||
[github.pat]
|
||||
# This is a personal token with access to the repositories and organizations
|
||||
# you plan on adding to garm. The "workflow" option needs to be selected in order
|
||||
# to work with repositories, and the admin:org needs to be set if you plan on
|
||||
# adding an organization.
|
||||
oauth2_token = "super secret token"
|
||||
[github.app]
|
||||
# This is the app_id of the GitHub App that you want to use to authenticate
|
||||
# with the GitHub API.
|
||||
# This needs to be changed
|
||||
app_id = 1
|
||||
# This is the private key path of the GitHub App that you want to use to authenticate
|
||||
# with the GitHub API.
|
||||
# This needs to be changed
|
||||
private_key_path = "/etc/garm/yourAppName.2024-03-01.private-key.pem"
|
||||
# This is the installation_id of the GitHub App that you want to use to authenticate
|
||||
# with the GitHub API.
|
||||
# This needs to be changed
|
||||
installation_id = 99
|
||||
# base_url (optional) is the URL at which your GitHub Enterprise Server can be accessed.
|
||||
# If these credentials are for github.com, leave this setting blank
|
||||
base_url = "https://ghe.example.com"
|
||||
# api_base_url (optional) is the base URL where the GitHub Enterprise Server API can be accessed.
|
||||
# Leave this blank if these credentials are for github.com.
|
||||
api_base_url = "https://ghe.example.com"
|
||||
# upload_base_url (optional) is the base URL where the GitHub Enterprise Server upload API can be accessed.
|
||||
# Leave this blank if these credentials are for github.com, or if you don't have a separate URL
|
||||
# for the upload API.
|
||||
upload_base_url = "https://api.ghe.example.com"
|
||||
# ca_cert_bundle (optional) is the CA certificate bundle in PEM format that will be used by the github
|
||||
# client to talk to the API. This bundle will also be sent to all runners as bootstrap params.
|
||||
# Use this option if you're using a self signed certificate.
|
||||
# Leave this blank if you're using github.com or if your certificate is signed by a valid CA.
|
||||
ca_cert_bundle = "/etc/garm/ghe.crt"
|
||||
Loading…
Add table
Add a link
Reference in a new issue