Commit 2bca97fa by Abhijit Menon-Sen

Explain the host range parsing changes in more detail

parent 2cda6d0e
...@@ -201,7 +201,11 @@ Minor changes: ...@@ -201,7 +201,11 @@ Minor changes:
* Many more tests, new API makes things more testable and we took advantage of it * Many more tests, new API makes things more testable and we took advantage of it
* big_ip modules now support turning off ssl certificate validation (use only for self signed) * big_ip modules now support turning off ssl certificate validation (use only for self signed)
* The undocumented semicolon-separated "pattern1;pattern2" syntax to match hosts is no longer supported. * Use "pattern1:pattern2" to combine host matching patterns. The undocumented
use of semicolons or commas to combine patterns is no longer supported.
* Use ``hosts: groupname[x:y]`` to select a subset of hosts in a group; the
``[x-y]`` range syntax is no longer supported. Note that ``[0:1]`` matches
two hosts, i.e. the range is inclusive of its endpoints.
* Now when you delegate a action that returns ansible_facts, these facts will now be applied to the delegated host, * Now when you delegate a action that returns ansible_facts, these facts will now be applied to the delegated host,
unlike before which they were applied to the current host. unlike before which they were applied to the current host.
* Consolidated code from modules using urllib2 to normalize features, TLS and SNI support * Consolidated code from modules using urllib2 to normalize features, TLS and SNI support
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment