Support `logs` command on a Job

Open
  • Is something wrong?
#233 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust
Domain
cli, devops

Research direction

Start at the implementation of the logs command and trace where the Logs only available on a pod error is produced. Compare the current resource handling with the stated kubectl logs job/<job-name> behavior, then verify that invoking logs for a Job returns its logs while existing pod behavior remains unchanged.

Written by the indexing model from the issue text.

Description

Currently this error message is returned: Logs only available on a pod

Why not have logs work for jobs as well, similar to: kubectl logs job/<job-name>

Dominant language
Rust
Stars
1.5k
Forks
93
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/click

All issues in databricks/click

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.