Skip to content

Add Projects::ProjectFeaturesChangedEvent event

Kassio Borges requested to merge kassio/add-project-features-changed-event into master

What does this MR do and why?

Context

As part of &7920 (closed), a new cache mechanism was added to Gitlab Pages internal API. This cache must be invalidated in many different situations, and for that we're using the Gitlab Event Store to dispatch/subscribe to these events.

This MR

This MR introduce the Projects::ProjectFeaturesChangedEvent event, which is one of the events required to invalidate the Gitlab Pages internal API cache (introduced in #363867 (closed)).

Another MR will use this event to invalidate the cache, like it was done in !92015 (merged)

Related to: #376298 (closed)

FAQ

  • Does it make sense to guard these changes under a FF?
    • The main feature, that will consume this event (following MR), is behind a FF (cache_pages_domain_api, introduced in !88956 (merged))

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Kassio Borges

Merge request reports