elastic/kibana

Fleet: disable package cache for development purposes

Open

#106,984 opened on Jul 28, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (8,021 forks)batch import
Team:Fleetenhancementgood first issue

Repository metrics

Stars
 (19,065 stars)
PR merge metrics
 (Avg merge 1d 16h) (999 merged PRs in 30d)

Description

While developing integrations it's a bit irritating to restart Kibana instance as some parts of a package are being cached.

For example - when modifying manifest's description, we don't have to restart Kibana. It's enough to reboot Package Registry with updated package.

But - when modifying policy templates, we have to artificially bump up the package version to make sure Kibana won't cache it (or rather load it for the first time).

The goal of this issue is to introduce a configuration property (option?) to disable package caching at all (only for development purposes).

cc @jen-huang @sayden

Contributor guide

Research direction
Explore the Fleet package caching mechanism in Kibana and introduce a configuration property (e.g., xpack.fleet.enableCache) that disables caching for development. Trace the cache usage in the PackageRegistry and ensure the property is respected.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70