In our environment, we have been experiencing several connection related
timeouts while using the om cli utility during the apply-changes task.
As of om 0.37.0, it provides the ability to configure both a connect and
a request timeout. This change allows both of those to be user
configurable within external pipelines.
[x] I have viewed signed and have submitted the Contributor License Agreement
[x] I have made this pull request to the master branch
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
In our environment, we have been experiencing several connection related timeouts while using the om cli utility during the apply-changes task. As of om 0.37.0, it provides the ability to configure both a connect and a request timeout. This change allows both of those to be user configurable within external pipelines.
[x] I have viewed signed and have submitted the Contributor License Agreement
[x] I have made this pull request to the
master
branch[ ] I have run all the unit tests