Skip to content

Flushing Cache when starting a content release could cause issues #23

@Sebobo

Description

@Sebobo
Member

Currently the Redis cache is flushed when a content release is started:

This is not optimal as the content release might start later due to the pipeline configuration and parallel running releases influence each other.
Therefore only the cache entries should be flushed which are somehow related to the started release.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

        Participants

        @Sebobo

        Issue actions

          Flushing Cache when starting a content release could cause issues · Issue #23 · Flowpack/Flowpack.DecoupledContentStore