Specifying `?master_timeout=-1` on an API which performs a cluster state
update means that the cluster state update task will never time out
while waiting in the pending tasks queue. However this parameter is also
re-used in a few places where a timeout of `-1` means something else,
typically to timeout immediately. This commit fixes those places so that
`?master_timeout=-1` consistently means to wait forever.
* Propagate ?master_timeout query parameter from crr put follow api
* Update docs/changelog/105168.yaml
* fix sily mistake
* spotless
* fix 2
* Add ?master_timeout query param to apis which use it
* Update rest api specs + yaml tests
* Add master_timeout (+timeout) to remaining api endpoints
* Update 105168.yaml
Correct message
* Enable randomly ?master_timeout param to ccr IT tests
* Add timeout param to RestCcrStatsAction
* propagate master_timeout param between put_follow -> resume_follow calls
* Propagate master_timeout down to persistent task layer
* Add transport version for ccr stats request object change
* Add BwC test for CcrStatsAction.Request obj
Removes `testenv` annotations and related code. These annotations originally let you skip x-pack snippet tests in the docs. However, that's no longer possible.
Relates to #79309, #31619
This commit is our first introduction to cross-cluster replication
docs. In this commit, we introduce the cross-cluster replication API
docs. We also add skelton docs for additional content that will be added
in a series of follow-up commits.
