salt

salt copied to clipboard

commit 8fd858ddf69c6ad000f0c31fcdff5feff599e939 (HEAD -> cachepillar, origin/cachepillar) Author: Matt Phillips [email protected] Date: Thu Apr 4 17:51:13 2024 -0400

PillarCache: reimplement using salt.cache

took the liberty of making it a proper subclass in the process. this now
uses the salt.cache infrastructure such that it can be driven by the
base cache driver or a different one if so desired. functionality should
be equivalent, including using the base bank=pillar key=minion_id for
merged pillar, such that minion_data_cache can take advantage of the
same cache. because we are updating the cache at the source, we no
longer need to update the cache in master/masterapi.

commit 4b20c8ded6e7d7983e981e94edae8f9fc5d935b0 Author: Matt Phillips [email protected] Date: Thu Aug 1 19:36:36 2019 -0400

fix minion data cache organization

previously 'bank' was minions/$minion, and key was 'data', which was a
merge of both pillar and grains. rather than do that, we organize pillar
and grains into separate banks for better index optimizations for
backends that can take advantage of it. it also just makes more sense
this way

commit fac04fccb3e6e46bcd2185003b0ff452f1e23644 Author: Matt Phillips [email protected] Date: Tue Apr 15 11:55:10 2025 -0400

salt.cache: allow cache.store() to set expires per key

rather than force a cache.cache() interface and a uniform expiry across
the cache, we add a more common per store() expiry that can also be used
instead or in addition to the original cache-wide expiry.

Merge requirements satisfied?

[NOTICE] Bug fixes or features added to Salt require tests.

• [ ] Docs
• [ ] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
• [ ] Tests written/updated

Commits signed with GPG?

Yes