[Feature Request] Support for Swarm Services update and deployment

[sandys]

A lot of us us Ouroboros to specifically deploy and update Swarm services. It is a boon to integrate with CI/CD frameworks.
Here's relevant discussion from ouroboros github issues - https://github.com/pyouroboros/ouroboros/issues/178

https://www.reddit.com/r/devops/comments/aizz0a/ouroboros_a_pythonbased_successor_to_watchtower/

I propose two ways of deployment - one is a continuous update every few minutes to the latest image available in the registry.
It would also be great if Portainer exposes a secure url for callbacks so that we can trigger specific updates. This url will receive very less information - for example 1) service/stack/task to update and image tag to pull for the update. The registry url, etc are hardcoded, so there's not a lot of security issues here.

[Duvel]

Have you seen the option "Service webhook" on a Service? With a cron job or the new tasks that could already help with the first requirement.

[sandys]

hi @Duvel
thanks for replying.
Two important points prevent this from being a full solution:

1. inbuilt scheduler rather than use an external cron. Ouroboros uses apscheduler to do this. you can use something like https://github.com/rakanalh/scheduler . Also - an inbuilt scheduler is better than a webhook because of threat
2. the security model of calling the webhook is unclear. an AWS style HMAC or a JWT would be best - https://docs.atlassian.com/DAC/bitbucket/concepts/understanding-jwt.html