< High-Level description of the feature ie: Executive Summary >

Goals

Currently a `get logs` request to Tekton Results for a PipelineRun's logs is not supported for the Blob log-backend. This isn't well-documented and some CLIs do not handle the error well; the `kubectl-tekton` CLI notably simply outputs that the server returned a 500 error...

We should support fetching the logs from a PipelineRun for this backend as we do for all other backends. There shouldn't be any technical limitations from this being possible.

Requirements

Out of scope

• The CLI's error messaging should be improved as well, but that is out of scope for this feature.

  Dependencies

- Documentation in the upstream CLI should be updated  

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

• There are no technical limitations to iterating over pipelinerun logs which are stored in S3

  Customer Considerations

• Tekton Results instances with heavy usage may have very slow queries, which could exceed request timeouts. We should ensure the timeouts cascade to any outbound requests (S3, database) and ensure any returned errors are useful to the caller.

  Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

What does success look like?

< Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>

QE Contact

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Impact

< If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment