-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
oc get pods --show-all=false -o name
doesn't work
#9901
Comments
What A quick solution would be to have an A better solution would be to call the same handler functions that What are your thoughts on this? |
No. Generic methods should be generic. Sounds like you should be filtering the list before calling the printer function, right? |
Filtering should happen before printing. On Mon, Aug 15, 2016 at 11:28 AM, David Eads notifications@github.com
|
Thanks for the feedback. I'll filter the list of resources as they're iterated through in get.go |
When you do that, you can also extract out the recent changes that went in On Tue, Aug 16, 2016 at 9:23 AM, Juan Vallejo notifications@github.com
|
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch adds a way to define resource-specific filters in order to handle this before they are sent to a printer handler, and implements a working filter handler for pods as an example.
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch adds a way to define resource-specific filters in order to handle this before they are sent to a printer handler, and implements a working filter handler for pods. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes: openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes/kubernetes#31163 Fixes openshift#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers.
UPSTREAM: kubernetes#31163 Fixes openshift/origin#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers. :100644 100644 cf7d1af... 185d31b... M pkg/kubectl/cmd/cmd_test.go :100644 100644 6551226... 99d7838... M pkg/kubectl/cmd/get.go :100644 100644 49ffb4d... 72d6c0f... M pkg/kubectl/cmd/util/factory.go :100644 100644 adc82b6... e42e819... M pkg/kubectl/cmd/util/helpers.go :100644 100644 892b30e... 78f11e4... M pkg/kubectl/resource/result.go :000000 100644 0000000... 8ca31d8... A pkg/kubectl/resource_filter.go :100644 100644 5af291e... 0b07610... M pkg/kubectl/resource_printer.go :100644 100644 2f341ac... cc04248... M pkg/kubectl/resource_printer_test.go
UPSTREAM: kubernetes#31163 Fixes openshift/origin#9901 Resources are currently filtered (in order to prevent printing) at print time in their HumanReadablePrinter handlers. This design makes it not possible to filter objects when they are printed using any other printer, such as YAML, JSON, or the NamePrinter. This patch removes any filters previously added at the printer level for pods and adds a way to define resource-specific filters before they are sent to a printer handler. A woking filter handler for pods has also been implemented. Filters affect resources being printed through the HumanReadablePrinter, YAML, JSON, and `--template` printers. :100644 100644 cf7d1af... 185d31b... M pkg/kubectl/cmd/cmd_test.go :100644 100644 6551226... 99d7838... M pkg/kubectl/cmd/get.go :100644 100644 49ffb4d... 72d6c0f... M pkg/kubectl/cmd/util/factory.go :100644 100644 adc82b6... e42e819... M pkg/kubectl/cmd/util/helpers.go :100644 100644 892b30e... 78f11e4... M pkg/kubectl/resource/result.go :000000 100644 0000000... 8ca31d8... A pkg/kubectl/resource_filter.go :100644 100644 5af291e... 0b07610... M pkg/kubectl/resource_printer.go :100644 100644 2f341ac... cc04248... M pkg/kubectl/resource_printer_test.go
The
--show-all=false
flag is documented as:However, when used together with
--output name
, all pods are listed, terminated pods are not omitted.Upstream bug
This bug was also filled in Kubernetes: kubernetes/kubernetes#29115
Version
Steps To Reproduce
In a new project, start a build like origin/examples/sample-app:
After the build is complete and the app is deployed, you should see two pods, one in
Completed
state, and the otherRunning
:Current Result
Now, the
--show-all
flag works with the default output, but doesn't when the output is set toname
:Expected Result
The text was updated successfully, but these errors were encountered: