Deprecate HTTP config service

[qwerty287]

As we have an addon system now, we can migrate http config services to them and remove support for http config services in the next major (so deprecate for now).

If you're currently using the http config service, you need to write the server yourself, there's only an example provided by us.
Then you can also write the addon I think. This is much faster than a HTTP request, simplifies typings and thus reduces errors etc. and does not require you to run an additional server.

Of course, we would need to update https://github.com/woodpecker-ci/example-config-service repository for this, I'm happy to open a PR for this.

[xoxys]

I tend to disagree and Im not sure yet if the addon system is really the way to go. The approach chosen by drone to extend parts by an external http service (https://docs.drone.io/extensions/overview/) is IMO way more flexible and easier do adopt by end users:

• extensions can be written in any language
• extensions are unrelated to the server version
• ...

[woodpecker-bot]

Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-3179.surge.sh

[qwerty287]

I get your point, however, there's also #915 in progress which will allow to use http extension per repo. I still think this should be supported, but on a global level, I'd replace it with addons.

[xoxys]

Per repo doesnt really scale in my opinion. Just wanted to add my experience with drone in the last year and the http extension system was quiet handy.

[6543]

I would also like to have it as core component.

[6543]

As long as we dont have a good way for plugins to:

1. Have core components work on windows too
2. Deliver them in a "cloud native way"

I'm strictly against relaying on them

[6543]

Plugins currently overload stuff instead of extending things. It"s great for thirdparty but not for our own components.