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

kops validate output yaml and json #3539

Closed
chrislovecnm opened this issue Oct 4, 2017 · 6 comments
Closed

kops validate output yaml and json #3539

chrislovecnm opened this issue Oct 4, 2017 · 6 comments
Labels
Feature Request good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@chrislovecnm
Copy link
Contributor

Would be awseom if kops validate would output yaml and json. I will update the issue with a couple ideas on the format.

@jatan28
Copy link
Contributor

jatan28 commented Oct 12, 2017

@chrislovecnm Are you thinking about something like kops validate cluster -o yaml, similar to the kubernetes get pod -o yaml?

@chrislovecnm
Copy link
Contributor Author

@jatan28 exactly :) We would need an output format, but you get the idea. Would be helpful for programmatically using validate.

@jatan28
Copy link
Contributor

jatan28 commented Oct 17, 2017

@chrislovecnm Do you have a design in mind for the output format? I saw that it is using print statements, is there an object that we can leverage for the structure of the output json/yaml. Once we finalize the design and approach, I can start working on it.

@chrislovecnm
Copy link
Contributor Author

I don't, come up with something and let's iterate

@jatan28
Copy link
Contributor

jatan28 commented Nov 20, 2017

@chrislovecnm What if we create a class for all the data that is getting rendered by this option, and then output it in yaml similar to kops edit cluster and json is fairly straightforward.

@dimitrovvlado
Copy link

I'm not sure if it would make sense, but what if kops get cluster includes a status field, similar to kubectl get pods?

@rifelpet rifelpet added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. and removed good-starter-issue labels Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

4 participants