Grzegorz Głąb

@SwapnilSoni1999 I believe nobody working on that actively and @antonmedv is open to accept incoming PR

I do not insist on specific format, I would like something which clearly distinct different resource types

Yes, definitely will be better. Could you also link here upstream issue ? Thank you :)

Yes, but I was basing on just `k get all` - indeed, adding `-oname` looks awful. Hope coloring will help.

I created PR with POC for helper function

hi @jordanwilson230 , if sth like this is ok with you I can dig it further : * detection of current shell * usage of external file (which can be...

This is POC for now. I am not bash/zsh programmer so I am not aware of consequences. I tested this function locally on bash and zsh and it was working...

please do not merge

no problem, good that you had time to carry this work :)

Maybe test like `promtool check metrics` [link](https://manpages.debian.org/testing/prometheus/promtool.1.en.html#check_metrics) or https://github.com/prometheus/client_golang/blob/main/prometheus/testutil/promlint/promlint.go can be used in CI to validate the metrics exposition format ?