Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5014

More flexible 'oc wait' command

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • oc
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      1. Proposed title of this feature request

      More flexible 'oc wait' command

      2. What is the nature and description of the request?

      Right now, 'oc wait' has limited way to checks, admitting just equal comparison, and not admitting filters. For example, a common check works:

      $ oc wait --for=jsonpath='{.spec.tags[0].from.name}'='quay.io/rhn_support_rauferna/httpd:1.0' is/testwait
      imagestream.image.openshift.io/testwait condition met 

      But it does not admit filters, or differente checks, like 'greater than' or 'different from' :

      $ oc wait --for=jsonpath='{.status.tags[?(@.tag == "10.0")].items[].image}'='quay.io/rhn_support_rauferna/httpd:1.0' is/testwait
      error: jsonpath wait format must be --for=jsonpath='{.status.readyReplicas}'=3
      
      oc wait --for=jsonpath='{.spec.tags[0].from.name}'!='quay.io/rhn_support_rauferna/httpd:1.0' is/testwait
      error: unexpected path string, expected a 'name1.name2' or '.name1.name2' or '{name1.name2}' or '{.name1.name2}'

      3. Why does the customer need this? (List the business requirements here)

      These options would help customers adding more logic to their CI/CD deployments, in scenarios where they need to wait for specific conditions to be met.

            gausingh@redhat.com Gaurav Singh
            rhn-support-rauferna Raul Fernandez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: