DevFW-CICD/garm
15
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

Make external provider less opinionated about executable

Browse source 
You can now specify the absolute path to a provider executable instead
of specifying a provider directory with a "garm-external-provider" in it.
This commit is contained in:
Gabriel Adrian Samfira 2022-07-16 17:29:45 +00:00
parent 5b651eeb3f
commit 95db6599ff
5 changed files with 37 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

7
testdata/config.toml vendored
View file

@ -170,9 +170,10 @@ provider_type = "external"
[provider.external]
# config file passed to the executable via GARM_PROVIDER_CONFIG_FILE environment variable
config_file = "/etc/garm/providers.d/azure/config.sh"
# path on disk to a folder that contains a "garm-external-provider" executable. The executable
# can be anything (bash, a binary, python, etc)
provider_dir = "/etc/garm/providers.d/azure"
# Absolute path to an executable that implements the provider logic. This executable can be
# 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