Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tail subcommand doesn't give any warning of a typo #11

Open
thepeterstone opened this issue Feb 26, 2018 · 3 comments
Open

tail subcommand doesn't give any warning of a typo #11

thepeterstone opened this issue Feb 26, 2018 · 3 comments

Comments

@thepeterstone
Copy link
Contributor

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.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/155537283

The labels on this github issue will be updated when the story is started.

@chombium
Copy link

chombium commented Oct 24, 2023

@thepeterstone this is not trivial to implement as the app names are unique in a space. Even if we try to the implement this, the name could be from another app. Therefore it is always better to use an app GUID instead of the app name ;)

@ctlong
Copy link
Member

ctlong commented Oct 27, 2023

I think there probably is a quality-of-life improvement where we could at least print a warning if nothing matches the source ID / app name.

e.g. "Warning: Provided source ID / app name does not match any source IDs in Log Cache or apps in this space."

@ctlong ctlong reopened this Oct 27, 2023
@ctlong ctlong moved this from Done to Waiting for Changes | Open for Contribution in Application Runtime Platform Working Group Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for Changes | Open for Contribution
Development

No branches or pull requests

5 participants