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
As a engineer
I want to be able to specify triggers that cobbler doesn't need to wait
so that I can get no 500 errors from apache/gunicorn
Provide a detailed description of the proposed feature
Now, if there is a trigger in cblr/svc/op/trig/mode/post/system/ or any other place for that matter
Which takes long time to complete, we will get 500 error from apache (since proxy request will timeout)
It would be good to have separate endpoint for async triggers or have some sort of argument that I can pass, so cobbler wouldn't wait for it to complete
Alternatives you've considered
Additional information
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
As a engineer
I want to be able to specify triggers that cobbler doesn't need to wait
so that I can get no 500 errors from apache/gunicorn
Provide a detailed description of the proposed feature
Now, if there is a trigger in
cblr/svc/op/trig/mode/post/system/
or any other place for that matterWhich takes long time to complete, we will get 500 error from apache (since proxy request will timeout)
It would be good to have separate endpoint for
async
triggers or have some sort of argument that I can pass, so cobbler wouldn't wait for it to completeAlternatives you've considered
Additional information
The text was updated successfully, but these errors were encountered: