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
If I set the environment variable ALLOW_RESTARTS=1 then permission is still denied for any stop/restart/kill operation due to them all being POST methods (blocked by default).
If I set the environment variable POST=1 then stop/restart/kill operations work even if ALLOW_RESTARTS=0.
Is this a bug or is ALLOW_RESTARTS a depreciated configuration? It is not in the README.md but it is still in the haproxy.cfg.
The text was updated successfully, but these errors were encountered:
Wondering the same here. I have to enable Post entirely even though all I need is restart. I was hoping to be able to be more granular by using ALLOW_RESTARTS=1 without POST=1.
I was looking at this same issue and it appears that the block for POST occurs in the rules before the allow statements for stop, start, and restart. That appears to be creating the situation where POST is still required since that rule is applied first. I believe the three new allow rules just need to be placed above the POST blocking rule and this should work as documented. Unfortunately it needs to be fixed in the repo, or you would need to build your own docker image. It isn't something that can be changed on the fly in the existing container image.
If I set the environment variable
ALLOW_RESTARTS=1
then permission is still denied for any stop/restart/kill operation due to them all beingPOST
methods (blocked by default).If I set the environment variable
POST=1
then stop/restart/kill operations work even ifALLOW_RESTARTS=0
.Is this a bug or is
ALLOW_RESTARTS
a depreciated configuration? It is not in theREADME.md
but it is still in thehaproxy.cfg
.The text was updated successfully, but these errors were encountered: