This release is NOT backward compatible with 1.0.4. All Varnish Controller components requires an upgrade.
The release includes bug fixes, new features and improvements.
In most cases, no configuration changes is required after upgrade. It will be enough to upgrade packages and make sure that the component services gets restarted.
/api/v1/ownerships(only accessible as system admin)
sort=<column>[:asc|desc](VCLI and API)
take=<limit>[,<offset>](VCLI and API)
-pfor password (support for ENV variables instead)
Since this is a major release, there are several things that breaks the interface in terms of output from VCLI. However, the REST API has not been changed in a breaking way, only appended to.
Deleted objects are no longer stored in database and the
-keep-deleted flag for Brainz has been
-p has been removed for specifying password to VCLI, the VCLI will either ask interactively for
password OR use the password specified in
The JSON output has been changed for VCLI (
-j will print the ASCII table for commands in
a more “JSON” fashion way with keys matching the table headers.
When updating a file or VCL that is linked to a deployed VCLGroup, the VCLGroup is no longer automatically deployed. You will need to manually trigger the deployment on the VCLGroup. This has been changed for preparing VCLGroups with the draft feature.
Sources for vcl/files must be base64 encoded when uploaded.
Note: No more releases will be available for version 1 of Varnish Controller.
See Varnish Controller Changelog for more details.
This update is recommended for all users.