Review the configuration parameters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
The Zowe extender was trying to increase the read timeout via the configuration option described in the documentation. Unfortunately, neither option worked. It would be good to review these parameters.
parameter that didn't work:
customMetadata.apiml.readTimeout
https://docs.zowe.org/stable/extend/extend-apiml/custom-metadata/
What eventually helped:
Set a timeout for the entire gateway in Zowe.yaml -> apiml.connection.timeout
Note
Looks like readTimeout is no longer recognized by the gateway and was replaced by responseTimeout, which didn't help as well.
Expected behavior
The timeout requested by the service is honored, and only valid configuration properties are documented.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the custom metadata documentation page linked in the issue and trace how customMetadata.apiml.readTimeout, responseTimeout, and apiml.connection.timeout are handled by the gateway. Confirm which properties are valid and whether the service-requested timeout is honored, then update the documentation and add or adjust coverage for the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100