Description
What would you like to be added?
We would like to request adding a configurable timeout flag to the OCM CLI.
When we run commands like ocm get cv ... (ref) from China, the CLI often times out while accessing component versions from global repositories because of slow and unstable network conditions. We tried adding our own retry logic and a timeout in our code, but the CLI’s internal timeout triggers first, so the retries never get a chance to run successfully.
Adding a timeout flag (e.g., --timeout) would allow users to increase or customize the timeout duration based on their network environment. This would make the CLI more reliable in regions with limited and weaker connectivity and avoid premature failures.
Why is this needed?
- The built-in timeout can’t be adjusted and fires before external retry logic can handle it.
- Network conditions in some regions require a longer timeout than the default.
- A configurable timeout would significantly improve usability and robustness for global users.
Thanks for considering this feature request.
Description
What would you like to be added?
We would like to request adding a configurable timeout flag to the OCM CLI.
When we run commands like
ocm get cv ...(ref) from China, the CLI often times out while accessing component versions from global repositories because of slow and unstable network conditions. We tried adding our own retry logic and a timeout in our code, but the CLI’s internal timeout triggers first, so the retries never get a chance to run successfully.Adding a timeout flag (e.g., --timeout) would allow users to increase or customize the timeout duration based on their network environment. This would make the CLI more reliable in regions with limited and weaker connectivity and avoid premature failures.
Why is this needed?
Thanks for considering this feature request.