Matt Riedemann a6fcfb28ae api-ref: document caveats with scheduler hints
I noticed this while working on change
I49ffebcd129990f1835f404d98b51732a32171eb and I realized
the scheduler_hints in the legacy filter_properties
dict is a bit different than what's in the RequestSpec
object, namely that the request validation schema is
per-hint. Some require a single value, like 'group', and
some accept a list of values, like 'different_host'.

Given how nebulous scheduler hints are, we should probably
note these in the API reference for the parameter, especially
because scheduler hints should not be considered interoperable.

Change-Id: I74114fc56bee2bebf4a5f5d6823ec968cad9a8e9
2017-10-30 16:14:28 -04:00
..
2017-06-07 21:05:12 +00:00
2017-05-23 17:17:52 +07:00
2016-11-11 14:01:51 -05:00
2017-03-31 06:19:01 +00:00
2017-09-07 15:42:31 +02:00
2017-04-27 22:28:01 -04:00
2017-05-04 16:13:45 +08:00
2017-03-29 01:37:56 +08:00
2017-09-07 15:42:31 +02:00
2017-09-07 15:42:31 +02:00
2017-09-07 15:42:31 +02:00
2017-07-13 11:40:43 +08:00
2017-09-07 15:42:31 +02:00