You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a webhook is called to run a systemd service, you simply get an HTTP 200 when the service has been started.
This issue suggests we optionally (as defined in the config) await the exit code of the service, and return a 200 or 500 depending on the exit code.
An example of why this is useful, is for github workflows. A workflow will await full deployment and can test it afterwards. If deployment failed, the workflow fails. If the workflow completed succesfully, you can expect to immediatly see the results. Full deployment experience!
The text was updated successfully, but these errors were encountered:
Currently, when a webhook is called to run a systemd service, you simply get an HTTP 200 when the service has been started.
This issue suggests we optionally (as defined in the config) await the exit code of the service, and return a 200 or 500 depending on the exit code.
An example of why this is useful, is for github workflows. A workflow will await full deployment and can test it afterwards. If deployment failed, the workflow fails. If the workflow completed succesfully, you can expect to immediatly see the results. Full deployment experience!
The text was updated successfully, but these errors were encountered: