Skip to content

Conversation

@carlossg
Copy link

to some CRDs

Continue and display the tree with the objects that we can access

@ahmetb
Copy link
Owner

ahmetb commented Jun 22, 2022

This should be a user visible warning if anything (not a -v=2).

Ideally we still fail, but the error can say "use -ignore-errors to continue", and that's when it works like this. What do you think?

@carlossg
Copy link
Author

should it force the user to always use the flag (it can be too annoying) or just print a line for each item that could not be fetched?

@ahmetb
Copy link
Owner

ahmetb commented Jun 24, 2022

I think printing warning can be ok, but ideally at least there should be a way to still fail if that's what a user wants.

@engelju
Copy link

engelju commented Mar 11, 2025

Sorry to bump this, is there any way to merge this?

@ahmetb
Copy link
Owner

ahmetb commented Mar 11, 2025

Sorry for the delay but I think we should make the error user-visible; not hidden behind-v=2 flag.

I use this plugin for exploration and last thing I'd want is silent omission of results.

to some CRDs

Continue and display the tree with the objects that we can access
@carlossg
Copy link
Author

carlossg commented Oct 5, 2025

this was fixed in #55 although not released

now it works although it is quite verbose with the forbidden errors

I have added here a --ignore-errors option if you wish to add it, but just a new release would be nice to have, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants