Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

EZP-30170: [VCL] Add own VCL for 2.5LTS to bump Varnish support there #77

Merged
merged 1 commit into from
Mar 1, 2019

Conversation

andrerom
Copy link
Contributor

@andrerom andrerom commented Feb 22, 2019

Copy link
Member

@mnocon mnocon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@andrerom andrerom requested a review from alongosz February 25, 2019 15:36
docs/varnish/vcl/varnish5.vcl Show resolved Hide resolved
@andrerom andrerom changed the title [VCL] Add own VCL for 2.5LTS to bump Varnish support there EZP-30170: [VCL] Add own VCL for 2.5LTS to bump Varnish support there Feb 25, 2019
@andrerom
Copy link
Contributor Author

@mnocon At this point it would have been great if meta used VCL from here, so there where cross testing ;)

Copy link
Member

@mnocon mnocon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andrerom yes, I will create a task for that, but we won't be able to tackle it before 2.5 is released.

//
// Make sure to at least adjust default parameters.yml, defaults there reflect our testing needs with docker.

vcl 5.1;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This value is not valid, according to docs it can be either 4.0 or 4.1: https://varnish-cache.org/docs/6.1/whats-new/upgrading-6.0.html#vcl-4-0-and-4-1

Varnish fails to starts with this VCL.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in a335b3d

I set it to 4.1 which seems more future proof, if you see any issues with that shout out :)

@andrerom andrerom force-pushed the drop_varnish4_from_2.5 branch from a335b3d to ab990e7 Compare March 1, 2019 10:14
@andrerom
Copy link
Contributor Author

andrerom commented Mar 1, 2019

Merging for now, to unblock meta PR.

@mnocon As discussed, could we have a follow up during certification so script in meta does install before building containers please so we can cover vcl and sorl config changes on travis behat runs in the future? /cc @lserwatka

# for free to join this conversation on GitHub. Already have an account? # to comment
Development

Successfully merging this pull request may close these issues.

3 participants