Problem/Motivation

To ensure performance with the Critical Data Elements API, add cache warming.

Issue fork drupal_purview-3574701

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

smulvih2 created an issue. See original summary.

nickolaj made their first commit to this issue’s fork.

nickolaj opened merge request !1

nickolaj’s picture

nickolaj
Primary language Ukrainian
commented
Status: Active » Needs review

Added cache warming for Critical Data Elements API calls. The CDE API client now uses the `cache.purview` bin (instead of `cache.default`) so CDE data is warmed and invalidated alongside other Purview caches. The `PurviewCacheWarmer::warm()` method iterates each governance domain and pre-populates the CDE query cache.

smulvih2’s picture

smulvih2
Location Canada 🍁
commented

@nickolaj this is great, thanks for MR! I will test this shortly today and merge in.

Are you using drupal_purview for a project?

  • nickolaj committed eb7a9bb0 on 1.0.x 
    Issue #3574701: Added cache warming for Critical Data Elements API...
smulvih2’s picture

smulvih2
Location Canada 🍁
commented
Status: Needs review » Fixed

This has ben confirmed working as expected. This will be included with the next release.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.