Skip to content

feature: Clean output of get-pod-ports #168

@mrlunchbox777

Description

@mrlunchbox777

Contact Details

mrlunchbox777@gmail.com

Feature Description

Limit the stdout of get-pod-ports.

Why?

It's unstable and difficult to parse programmatically as is.

What should happen?

This should depend on the move to golang because it'll be easier to abstract.

The output should be limited to some json/yaml that provides what an end user might need/want.

Covers this TODO.

Steps to Test

These should be refined as it becomes more obvious what an end user might want.

  1. Assuming the bsctl command to call this function is foobar and you have run the create-test-pod command, calling foobar -l "app.kubernetes.io=test-pod" | yq .items[0] shouldn't return an error or null.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions