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

Sonolark types not always intuitive #139

Open
johnSchnake opened this issue Apr 27, 2022 · 1 comment
Open

Sonolark types not always intuitive #139

johnSchnake opened this issue Apr 27, 2022 · 1 comment
Labels

Comments

@johnSchnake
Copy link
Contributor

When doing a kube.get you get a string rather than something you can iterate over or reference fields of. This makes it really hard to work with intuitively (if at all)

@johnSchnake
Copy link
Contributor Author

For example I had to do this:

def getPods():
    podsString = kube.get(pod="kube-system/")
    podsDecode = yaml.decode(podsString)
    return struct.encode(podsDecode)

When I think the first thing it should return are objects and we turn them to plain yaml if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant