Improve logging in Deploy raw Kubernetes YAML steps

My team is using the “Deploy raw Kubernetes YAML” step template and we’d like to see some improvements in its logging.

The issues we’ve noticed so far:

  • the Info messages (those shown in Task Log) contain a bunch of “No resources found” messages which are confusing as we don’t know what they refer to or if they indicate a problem of some kind:

    Deployment/foo created 
    deployment.apps/foo configured 
    service/foo unchanged 
    ingress.extensions/foo unchanged 
    No resources found 
    No resources found 
    No resources found 
    No resources found 
    Deleting old Deployment resources 
    No resources found 
    No resources found 
    
  • The raw log includes the deployed YAML file content, but it is repeated twice, making the log unnecessarily long. Is there a reason for that?

    07:46:14   Verbose  |       Invoking target script "/usr/local/etc/octopus/Work/20200916074608-194686-1495/Script.sh" with  parameters
    07:46:14   Verbose  |       the
    07:46:14   Verbose  |       whole
    07:46:14   Verbose  |       YAML
    07:46:14   Verbose  |       goes
    07:46:14   Verbose  |       here
    07:46:14   Info     |       Deployment/octopus-utilities created
    07:46:14   Verbose  |       the
    07:46:14   Verbose  |       whole
    07:46:14   Verbose  |       YAML
    07:46:14   Verbose  |       goes
    07:46:14   Verbose  |       here
    07:46:15   Info     |       deployment.apps/foo configured
    07:46:15   Info     |       service/foo unchanged
    07:46:15   Info     |       ingress.extensions/foo unchanged
    
  • The YAML included in raw log is stripped from all leading whitespaces, losing all indentation, making it really hard to read.

It would be great to see some improvements in this area, deployment logging is very important when something goes wrong.

Hi @jakub.januszkiewicz,

Thanks for getting in touch!

These are some good suggestions and would definitely make this area better. I’ve raised this with our engineers for review.

Regards,
Paul