Implement build/deploy log support

[smlx]

This change adds support for build and task logs and relies on uselagoon/lagoon-ssh-portal#570.

The logs command gets two new flags. The idea is that you can specify --task to get logs from all running tasks, or --task=name if you know the name.

  -b, --build string[="all_builds"]   specify build logs, with an optional specific build name
  -t, --task string[="all_tasks"]     specify task logs, with an optional specific task name

The deploy subcommands also gets new flags --follow that stream deploy logs until the deployment completes.

      --follow                 Follow the deploy logs

I have no idea if this is a good developer UX: feedback requested.

I have tested this manually using the deploy latest subcommand, but have not actually tested the other subcommands because I don't have a good test environment for them. Please let me know if they are broken! In particular, the code relies on the resultData.Result being the name of the build. This holds for deploy latest, but I don't know if it holds for other subcommands?

# tested and working
go run . logs -p test-project -e main --build
go run . logs -p test-project -e main --build=lagoon-build-123xyz
go run . logs -p test-project -e main --task
go run . logs -p test-project -e main --task=lagoon-task-123xyz
go run . deploy latest -p test-project -e main --follow --force

# untested - please test!
go run . deploy branch -p test-project -e main --follow --force
go run . deploy promote -p test-project -e main --follow --force
go run . deploy pullrequest -p test-project -e main --follow --force

[shreddedbacon]

Error returned for a task or build that doesn't have a pod that exists in the namespace needs to be clearer that the pod does not exist anymore to prevent confusion from users when the pod is no longer available

$ go run main.go -l local-k3d logs -p lagoon-demo -e main --task=lagoon-task-qmpun
log stream interrupted. SID: 1ca4add8febb162924d3499578eda5f8e8c8b6cfd57d461711fd2cd940861aca
Error: Process exited with status 253exit status 253

$ go run main.go -l local-k3d logs -p lagoon-demo -e main --build=lagoon-build-def456
log stream interrupted. SID: 4e2063997870bf1c3d83de52874b2ddea0082386764f3abdf865591b86d0a31b
Error: Process exited with status 253exit status 253

Maybe this is something the ssh-portal should handle though

[smlx]

Error returned for a task or build that doesn't have a pod that exists in the namespace needs to be clearer that the pod does not exist anymore to prevent confusion from users when the pod is no longer available

Good idea!

$ go run main.go -l local-k3d logs -p lagoon-demo -e main --task=lagoon-task-qmpun
log stream interrupted. SID: 1ca4add8febb162924d3499578eda5f8e8c8b6cfd57d461711fd2cd940861aca
Error: Process exited with status 253exit status 253

$ go run main.go -l local-k3d logs -p lagoon-demo -e main --build=lagoon-build-def456
log stream interrupted. SID: 4e2063997870bf1c3d83de52874b2ddea0082386764f3abdf865591b86d0a31b
Error: Process exited with status 253exit status 253

Maybe this is something the ssh-portal should handle though

Yep, I added this feature over on uselagoon/lagoon-ssh-portal#570.

It now looks like:

$ go build . && ./lagoon-cli logs -p demo -e demoenv --task=lagoon-task-banana
no pods matched selector. SID: 74c27e22b7820980157f08938c642ae55d8201b38a259d4628c21c7aacc047f2
Error: Process exited with status 253

[smlx]

Based on the suggestion in uselagoon/lagoon-ssh-portal#570 (comment) I added --show-pod and --show-timestamp flags to the logs and deploy commands. Both default to true at the moment (so no change in behaviour), but let me know if you think that should be changed 🙂