Skip to content

varnishreload should clean up old VCLs by default #171

Open
@Bilge

Description

@Bilge

Although varnishreload supports cleaning up after itself (with the -m option), most people will probably never discover this, and regardless of whether they do or not, it seems to me it should be the default behaviour to keep a maximum (e.g. of 5 or 10) VCLs around to avoid memory and disk usage growing indefinitely.

Personally I don't really see the need to keep any old VCLs around, because it seems to me the normal use-case should be deploying a new VCL and reloading each time one wishes to make a change, even if that change happens to be a rollback, rather than attempting to reference one of the pseud-randomly generated VCL reload names and hoping you happen to roll back to the correct one despite the unclear moniker, but I respect there may be use-cases I have not considered that find value in such rollback facility. Nevertheless, it should not be practical to ever roll back more than 5, conservatively, or 10 at the absolute most, so the default should be somewhere in this region.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions