Please make webhook urls more scriptable

[Daemach]

I am working on creating a local dev env that uses a powershell script to build all of my containers. I'm running a stack locally since I have to mimic the production env. After rebuilding the containers and pushing them to the local registry I would like to be able to call the webhook for the services to update them but the webhook urls are currently not scriptable.

http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c

Maybe this is a security issue - generating a guid for the stack then allowing me to specify service name may be an answer. Then at least I could update a single variable in a script file if the stack changes. I need something like this:

http://192.168.59.94:9000/api/webhooks/stack_service
http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c/service
http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c/stack_service
http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c/stack/service

[deviantony]

Have a look at existing feature requests for webhooks when you can and feel free to comment in any or close this one if you feel like it might be used somewhere: https://github.com/portainer/portainer/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fwebhooks

[Daemach]

Thanks for reopening this.

I need to set up a staging environment now and would very much like to be able to just copy and paste and change the service name. The nice thing about URLs is that you should be able to support a number of different interfaces based on the user's preferences. If they want max security, for a production environment, for example, the current system should be ok. If they need more flexibility, for a dev/staging environment, a URL such as http://192.168.59.94:9000/api/webhooks/update/stack/service would be MUCH easier to deal with, especially when deleting and recreating the stack is necessary. I have to do this frequently when troubleshooting clustering issues since docker does not allow switching directly from replica to global mode.

And on that note, if http://192.168.59.94:9000/api/webhooks/update/stack was able to update ALL of the services in a stack at one time it would be immensely helpful in development.

Finally, are you able to look for metadata in compose files and take action based on the content (so my lazy posterior can just copy and paste stack files instead of creating all of this manually)?

version: "3.7"

#portainer 
#  webhooks:
#    enable:  (enables and creates webhooks automatically)
#      - true/false
#      - stack ( just stack webhook - all services at once )
#      - service ( individual service webhooks based on mode )
#      services:
#         - service1
#         - service2
#    mode:
#      - simple ( creates http://192.168.59.94:9000/api/webhooks/update/stackname/servicename )
#      - secure ( creates http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c or http://192.168.59.94:9000/api/webhooks/6f9b856c-29ea-416d-8719-c39bfd7aee5c/stackname/servicename )

services:
  mywebsite:
    etc.