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
Is your feature request related to a problem? Please describe.
running the lagoon deploy command says success immediately without knowing the results of the deployment
Describe the solution you'd like
I would like to watch the deployment logs (the same that are viewable in lagoon UI) live as they are happening. Maybe a --watch flag?
Additional context
I ran a deployment with the cli and it said success. The deployment failed however.
The text was updated successfully, but these errors were encountered:
Currently, there is no way to stream the log output live from lagoon :(
At the moment, the best that can be done is to start a deployment, then poll the api for the status of the deployment until it completes. Once complete, it could dump the build log in one hit.
#294 changes the lagoon get deployment command to accept the build name. This hasn't been released yet, but it will be soon.
This will return the build after it has been triggered, you could after triggering the build wrap it in a loop that checks the output of the get deployment for the status then
get deployment also has the --logs flag to return the logs, but doing this repeatedly is kind of pointless because they only update when there are periodic status changes.
I'm going to close this issue out, as the release that contains this is being bundled at the moment.
Is your feature request related to a problem? Please describe.
running the lagoon deploy command says success immediately without knowing the results of the deployment
Describe the solution you'd like
I would like to watch the deployment logs (the same that are viewable in lagoon UI) live as they are happening. Maybe a
--watch
flag?Additional context
I ran a deployment with the cli and it said success. The deployment failed however.
The text was updated successfully, but these errors were encountered: