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.
It can then decide to acnowledge the current configs (By returning **HTTP 204**), or overriding the configurations and returning new ones in the response
This service is written in go, to run it first copy the config example: `cp .env.example .env`
Adjust the secret and add a filtering regex. The repositories that have a name match the filtering regex will receive the config from `central-pipeline-config.yaml`, while all other repositories will continue using their original configuration.
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)