[master] 48bb211 fix shard director upgrade notes

Nils Goroll nils.goroll at uplex.de
Thu Mar 15 09:35:11 UTC 2018

commit 48bb211b22f54791abe30e086be9b0d50a6fdbf4
Author: Nils Goroll <nils.goroll at uplex.de>
Date:   Thu Mar 15 10:33:41 2018 +0100

    fix shard director upgrade notes

diff --git a/doc/sphinx/whats-new/upgrading-6.0.rst b/doc/sphinx/whats-new/upgrading-6.0.rst
index 973ac3b..4dbc4ae 100644
--- a/doc/sphinx/whats-new/upgrading-6.0.rst
+++ b/doc/sphinx/whats-new/upgrading-6.0.rst
@@ -486,10 +486,15 @@ for advice on how to do so.
 With the ``resolve=LAZY`` argument of the ``.backend()`` method, the
 shard director will now defer the selection of a backend to when a
 backend connection is actually made, which is how all other bundled
-directors work as well. This enables layering the shard director below
-other directors -- you can use ``.backend(resolve=LAZY)`` to set the
-shard director as a backend for another director. ``resolve=LAZY``
-MUST be used in ``vcl_init`` and on the client side.
+directors work as well.
+In ``vcl_init``, ``resolve=LAZY`` is default and enables layering the
+shard director below other directors -- you can now use something like
+``mydirector.add_backend(myshard.backend())`` to set the shard
+director as a backend for another director.
+Use of ``resolve=LAZY`` on the client side is limited to using the
+default or associated parameters.
 The shard director now provides a ``shard_param`` object that serves
 as a store for a set of parameters for the director's ``.backend()``

More information about the varnish-commit mailing list