sebclem/woodpecker-config-service
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Readme hightlighting

Browse Source 
Signed-off-by: Lukas Bachschwell <lukas@lbsfilm.at>
This commit is contained in:
Lukas Bachschwell 2022-02-27 22:38:42 +01:00
parent 15d46541e2
commit 48564b0271
No known key found for this signature in database
GPG Key ID: CCC6AA87CC8DF425
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Readme.md
View File

@ -1,8 +1,8 @@
# Woodpecker CI Configuration Service example # Woodpecker CI Configuration Service example
This repository provides a very simplistic example of how to set up an external configuration service for Woodpecker CI This repository provides a very simplistic example of how to set up an external configuration service for **Woodpecker CI**
The external service gets a HTTP POST request with information about the repo, current build, and the configs that would normally be used. The external service gets a **HTTP POST** request with information about the repo, current build, and the configs that would normally be used.
It can then decide to acnowledge the current configs (By returning HTTP 204), or overriding the configurations and returning new ones in the response It can then decide to acnowledge the current configs (By returning **HTTP 204**), or overriding the configurations and returning new ones in the response
Usecases for this system are: Usecases for this system are:
- Centralized configuration for multiple repositories at once - Centralized configuration for multiple repositories at once
@ -13,7 +13,7 @@ Adjust the secret and add a filtering regex. The repositories that have a name m
Then run using `go run .`. Then run using `go run .`.
Make sure to configure your woodpecker instance with the correct endpoint and configure the same secret. See [Woodpeckers documentation here](https://woodpecker-ci.org/docs/administration/external-configuration-api) Make sure to configure your woodpecker instance with the correct **endpoint** and configure the same **secret**. See [Woodpeckers documentation here](https://woodpecker-ci.org/docs/administration/external-configuration-api)
eg: eg: