Skip to content

Allow selective cache re-poisoning #2

@AdnaneKhan

Description

@AdnaneKhan

There are some cases where a job sets a new cache entry that Cacheract has not poisoned yet. However, if Cacheract runs off of a previous cache hit, it will not try to re-infect caches that are already set.

There should be a way to configure an optional regular expression to capture cache entries that might be set after the initial Cacheract infection. If any keys match the regular expression, Cacheract will try to clear and re-set the entry even if it is on a subsequent cache hit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions