Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
bcd7d07a
Commit
bcd7d07a
authored
Feb 24, 2020
by
Nils Goroll
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
upgrading 6.3: vcl auto state details
parent
2b127d43
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
1 deletion
+21
-1
upgrading-6.3.rst
doc/sphinx/whats-new/upgrading-6.3.rst
+21
-1
No files found.
doc/sphinx/whats-new/upgrading-6.3.rst
View file @
bcd7d07a
...
@@ -14,7 +14,27 @@ features are listed in "Changes". Explicitly mention what does *not*
...
@@ -14,7 +14,27 @@ features are listed in "Changes". Explicitly mention what does *not*
have to be changed, especially in VCL. May include, but is not limited
have to be changed, especially in VCL. May include, but is not limited
to:**
to:**
TODO: a word on VCL temperature and the ``auto`` change.
For users of many and/or labeled VCLs
=====================================
Users of the advanced mechanics behind the ``vcl.state`` CLI command
(most likely used via ``varnishadm``) should be aware of the following
changes, which may require adjustments to (or, more likely, allow for
simplifications of) scripts/programs interfacing with varnish:
The VCL ``auto`` state has been streamlined. Conceptually, it used to
be a variant of the ``warm`` state which would automatically cool
the vcl. Yet, cooling did not only transition the temperature, but
also the state, so ``auto`` only worked one way - except that
``vcl.use`` or moving a label (by labeling another vcl) would also set
``auto``, so a manual warm/cold setting would get lost.
Now the ``auto`` state will remain no matter the actual temperature or
labeling, so when a vcl needs to implicitly change temperature (due to
being used or being labeled), an ``auto`` vcl will remain ``auto``,
and a ``cold`` / ``warm`` vcl will change state, but never become
``auto`` implicitly.
For developers and authors of VMODs and API clients
For developers and authors of VMODs and API clients
===================================================
===================================================
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment