[Varnish] #1679: After upgrade, custom vmods are not moved so vcl does not compile

[Varnish]

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
 Reporter:  razvanphp  |       Owner:  lkarsten
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  vmod       |     Version:  4.0.3
 Severity:  normal     |  Resolution:  fixed
 Keywords:             |
-----------------------+-----------------------

Comment (by razvanphp):

 Ok, so I just updated an older 4.0.2 to 4.0.3-2~wheezy, everything is ok,
 but the vmods dir is back to `/usr/lib/varnish/vmods`. Is this how it
 should be?

 I'm asking to know how to write my ansible scripts. Or.. is it a better
 way to programmatically get the vmods dir?

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:4>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator