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
Hi, I recently wrote a script to force a redeployment of a stack through the komodo api. For that I ran PullStack and afterwards DeployStack, the reason beeing their respective api description which say the first runs docker compose pull and the second one docker compose up. Therefore, I have to pull before if up the stack with a new container verion. So far so good. It works just fine, but I then saw the stack logs for the deploy showing a step that pulls the image before upping the stack. Not running PullStack therefore should and does work just fine, but it is not straightforward, that this is the resulting behaviour. Is this intended and the api docs are incorrect?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I recently wrote a script to force a redeployment of a stack through the komodo api. For that I ran PullStack and afterwards DeployStack, the reason beeing their respective api description which say the first runs
docker compose pull
and the second onedocker compose up
. Therefore, I have to pull before if up the stack with a new container verion. So far so good. It works just fine, but I then saw the stack logs for the deploy showing a step that pulls the image before upping the stack. Not running PullStack therefore should and does work just fine, but it is not straightforward, that this is the resulting behaviour. Is this intended and the api docs are incorrect?Beta Was this translation helpful? Give feedback.
All reactions