Update inactivity_timeout to integer type with min/max constraints #530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates the
inactivity_timeoutparameter in the Streaming API specification (usm-streaming.yml) to correctly document it as an integer type with minimum value of 5 and maximum value of 3600 seconds.Changes:
type: integer,minimum: 5,maximum: 3600Review & Testing Checklist for Human
inactivity_timeoutparameter/docs/api-reference/streaming-api/streaming-api#request.query.inactivity_timeoutto confirm the type shows as integer and min/max constraints are displayed correctlyNotes