@elbandi could you please submit a PR?

i think, the squid access log doesnt go to the log/messages.
And sorry, i wasnt accurate. this is the issue: access log is in var/log/squid3/ directory not in var/log/squid/.
two file is affected: https://github.com/vyos/vyatta-webproxy/blob/current/templates-op/show/webproxy/log/node.def and https://github.com/vyos/vyatta-webproxy/blob/current/templates-op/monitor/webproxy/access-log/node.def

That part is rewritten in current already. https://github.com/vyos/vyos-1x/blob/current/op-mode-definitions/show-log.xml#L212

https://github.com/vyos/vyatta-webproxy/pull/16

@dmbaturin Did you forget to merge the other PRs (migration code) ?

A new description could be:

Or drop by our slack channel for help

First you need to specify a new version of your subtree,
https://github.com/vyos/vyatta-cfg-system/commit/f68dda9d619ea74bed266122ac86604284e1a9e4

Ok. Fine. Can you give me a hint about docu and an example of such a migration script? So I'll try to implement one for this case: Migrate from webproxy proxy-bypass 1.2.3.4/24 to webproxy whitelist destination-address 1.2.3.4/24

@dsteinkopf I think almos every command is good when there is a discussion ongoing and we can agree on somehing. VyOS has so called migration scripts which are executed once we do CLI changes and thus migrate old configuration nodes to new ones. We already make use of this feature alot and it is transparent to the user.

Thank you for your positive feedback. I am open to all changes.
We can rename the command, of course. But let us think about this shortly:

I really like the idea and thank you for the contribution.

@dmbaturin you want too look into this

That change should be safe to merge because it just adds a command and doesn't change anything else. So no one will be using this at the moment and so it won't have any impact. So I'd be happy to see it in 1.2.0.