OSD-23744: make context cmd quicker

[Tof1973]

• Some actions which were done in sequence are now done in parallel
• We are now retrieving the cluster from OCM only one time in the process while it was done twice
• before running the OCM query to retrieve cluster, we now detect first what is the cluster identifier, in order to make the query quicker
• Add verbose output with delay for each action in order to be able to troubleshoot easily when command is taking time

With those changes we move from a frequent context of more than 10s (and sometime much more) to a context of less than 5s most of the time ;)

[openshift-ci-robot]

@Tof1973: This pull request references OSD-23744 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

• Some actions which were done in sequence are now done in parallel
• We are now retrieving the cluster from OCM only once in the process while it was done twice
• Add verbose output with delay for each action in order to be able to troubleshoot easily when command is taking time

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Tof1973: This pull request references OSD-23744 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

• Some actions which were done in sequence are now done in parallel
• We are now retrieving the cluster from OCM only once in the process while it was done twice
• Add verbose output with delay for each action in order to be able to troubleshoot easily when command is taking time

With those changes we move from a frequent context of more than 10s (and sometime much more) to a context of less than 5s most of the time ;)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Tof1973: This pull request references OSD-23744 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

• Some actions which were done in sequence are now done in parallel
• We are now retrieving the cluster from OCM only once in the process while it was done twice
• before running the OCM query to retrieve cluster, we now detect first what is the cluster identifier, in order to make the query quicker
• Add verbose output with delay for each action in order to be able to troubleshoot easily when command is taking time

With those changes we move from a frequent context of more than 10s (and sometime much more) to a context of less than 5s most of the time ;)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Tof1973: This pull request references OSD-23744 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

• Some actions which were done in sequence are now done in parallel
• We are now retrieving the cluster from OCM only one time in the process while it was done twice
• before running the OCM query to retrieve cluster, we now detect first what is the cluster identifier, in order to make the query quicker
• Add verbose output with delay for each action in order to be able to troubleshoot easily when command is taking time

With those changes we move from a frequent context of more than 10s (and sometime much more) to a context of less than 5s most of the time ;)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[AlexVulaj]

/label tide/merge-method-squash

[AlexVulaj]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlexVulaj, Tof1973

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AlexVulaj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@Tof1973: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.