cloudfoundry / cloudfoundry/log-cache-cli
tail subcommand doesn't give any warning of a typo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 16
- Avg merge
- 9h 18m
- Merged PRs (30d)
- 7
Description
If I had the app logspinner, but did the command for cf log-cache tail logzpinner, it would succeed. It looks like it assumes that I am looking for a bosh component and therefore doesn't complain.
However, we could look at meta, and give a warning that the given source-id doesn't exist in log-cache.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the cf log-cache tail subcommand and trace how it handles the source-id shown in the reproduction. Read the metadata lookup for log-cache sources, then verify the behavior with the logzpinner typo. Done means an unknown source-id produces a warning instead of silently succeeding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100