qoliber/trident-cache-magento2

Changelog

All notable changes to Qoliber_TridentCache will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

From v1.4.0 the module version tracks the Trident engine version it integrates
with (e.g. module 1.4.0 ↔ Trident 1.4.0).

[1.5.2] - 2026-07-23

Versioning: re-syncs the module to the current engine — it pairs with
Trident 1.5.2. The jump from 1.4.0 to 1.5.2 folds in the 1.5.0
observability admin-API surface (built earlier but never released) plus the
client-reliability fixes below.

Added — Trident 1.5.0 observability admin surface

• Admin screens + TridentClient methods for the 1.5.x admin API: status
  (/admin/status), explain (/admin/explain), Reflect (status/queue/
  enable/disable), Launch, Cache Warmer, Backends (drain/restore),
  Bans, DNS discovery, and Denoisers — matching Trident's OpenAPI
  spec. Integration test coverage for the client, config, observers, and plugins.

Fixed — admin-API client reliability (Model/TridentClient.php)

• Every request now applies connect + read timeouts (5s/10s). Previously
  most methods (including the observer-triggered purgeTags/purgeAll that run
  synchronously on the storefront) issued curl calls with no timeout, so an
  unreachable or wedged Trident admin port could hang a Magento admin save or a
  storefront Type::clean.
• The shared-Curl DELETE verb can no longer leak. Every request re-pins
  CURLOPT_CUSTOMREQUEST via prepareRequest(), so a prior DELETE cannot cause
  a following GET/POST on the injected singleton Curl to be issued as a DELETE.
• The admin API token is now required to enable purges. With FPC on engine 3
  but no api_token set, the client no longer fires empty-Bearer 401s that
  were swallowed into permanent stale content — it disables cleanly and logs one
  distinct, debug-independent warning so the misconfiguration is visible.
• Non-2xx admin responses are logged (401/5xx) instead of being silently
  discarded, on every request path.

Known follow-ups (not in this release)

• POST-gate the mutating admin controllers (HttpPostActionInterface) and add a
  form_key to each admin POST form — requires validation in a Magento
  environment; adminhtml URL secret-keys already provide CSRF protection.
• Align tag casing between the two purge trigger paths.
• Remove dead surfaces (PurgeStrategy is ENABLED=false; ttl_static is read
  but never applied).

[1.4.0] - 2026-06-16

Versioning: this release realigns the module version with the Trident
engine — it pairs with Trident 1.4.0. The jump from 1.2.x to 1.4.0 syncs
the two; future releases will continue to match the engine version.

Fixed — admin API parity with Trident's OpenAPI spec

The admin parity screens added in 1.2.0 were corrected to read Trident's actual
admin-API response fields. Several referenced names that do not exist (so
columns rendered blank or wrong), and two write calls used the wrong shape:

• DNS Discovery — read backend_name / hostname / addresses /
  stats.last_success (were name / dns_name / resolved_addresses /
  last_refresh); "resolving" status is derived from resolved addresses.
  TridentClient::refreshDiscovery() now sends the required name query param,
  and the Refresh action re-resolves every discovered target.
• Bans — read ban_type / active / affected (were type /
  expires_at); TridentClient::createBan() sends type (was ban_type);
  ban types are url / tag / pattern — the invalid host type was removed.
• Backends — per-backend cards use host:port / status /
  total_requests / total_errors / avg_response_ms / active_connections
  (were url / drained / weight / avg_latency_ms); connection pools read
  name / max / queued (were backend / max_connections /
  waiting_requests).
• Cache Warmer — last-run "Finished At" reads completed_at (was finished_at).
• Statistics — latency request count reads count (was request_count).

This brings the 1.2.0 admin feature parity and the 1.2.1 Cache Coverage screen
(both below) to their first correctly-rendering release.

[1.2.1] - 2026-06-07

Added

• Cache Coverage (trident/cache/coverage) — paste a list of URLs and see which
  are currently cached (freshness/age/TTL/size) plus the overall cached percentage,
  via the new POST /admin/cache/coverage endpoint (TridentClient::cacheCoverage()).
  Useful for verifying a warm run landed. Accessible via System > Trident Cache >
  Cache Coverage.

[1.2.0] - 2026-06-04

Added — admin feature parity with the Trident admin panel

Brings the full Trident operator surface into the Magento backend (System > Trident Cache).
Each screen follows the existing controller/ViewModel/template/ACL pattern and talks to the
admin API through Model\TridentClient (extended with ~30 new methods + shared GET/POST/DELETE helpers).

• Cache Warmer (trident/warmer) — status (state, current-run progress, last-run summary),
  Run-now (optional URL list), Cancel.
• Launch Mode (trident/launch) — start (URL list, auto-complete, bypass IPs), live state +
  progress, complete (go-live), abort.
• Reflect Mode (trident/reflect) — emergency origin shield; enable (full/selective/ttl_extension
  • duration/reason), disable (replay = hard-purge, or soft-purge = mark stale for lazy
    revalidation), queued-purge view, active warning banner.
• Denoisers (trident/denoisers) — query-scope + path-zone report, per-row pin/unpin/reset, WAF export.
• Bans (trident/bans) — list active/expired soft-purge bans, create (url/tag/host), delete.
• Backends (trident/backends) — per-backend health cards (drain/restore) + connection-pool table.
• DNS Discovery (trident/dns) — discovered targets table + refresh.
• Live Events (trident/events) — poll-based console over the SSE streams (requests/cache/backends/errors).
• Richer Statistics — latency percentiles, recent errors, protection summary, BP-59 memory layout.
• Expanded Purge — purge by host and by Vary (in addition to all / tags / url / pattern).

[1.1.0] - 2026-03-06

Added

• Cached Pages admin page — Paginated grid of all cached URLs with host, method, size, TTL, age, hits, and tags. Accessible via System > Trident Cache > Cached Pages.
• Cache Tags admin page — Paginated list of all cache tags with entry counts. Accessible via System > Trident Cache > Cache Tags.
• Tag filtering on entries — Filter cached entries by tag via the entries page filter form.
• Tag prefix filtering — Filter cache tags by name prefix on the tags page.
• Per-entry purge — AJAX purge button on each cache entry row for targeted invalidation.
• Per-tag purge — AJAX purge button on each tag row to purge all entries with that tag.
• Clickable tag badges — Tag badges on entries link to entries filtered by that tag.
• "View Entries" on tags — Link from each tag to the entries page filtered by that tag.
• Top URLs on stats page — Top 10 URLs by request count table on the Cache Statistics page.
• Sorting — Sort entries by age, size, hits, or TTL. Sort tags by count or name.
• TridentClient API methods — Added getEntries(), getTags(), getTopUrls(), purgeUrl().
• Configurable TTL, grace period, and static asset TTL via admin system configuration.
• ESI (Edge Side Includes) support — Enable ESI processing with configurable max nesting depth. Adds Surrogate-Control header when enabled.
• ConfigTypePlugin — Maps Trident cache type (3) to Varnish (2) so core Magento FPC plugins activate without patching core code.
• Health indicator on Cache Management page — Green/orange status dot with Trident version and uptime display.
• Unit and integration test suite — PHPUnit 10.5 tests for TridentClient, Config, all plugins, observers, and PurgeStrategy.
• Vary dimension badges — Cache entries with the same URL but different vary values (e.g. customer groups) now show distinguishing badges.

Changed

• ResponsePlugin rewritten — Now uses admin-configured TTL for s-maxage and grace period for stale-while-revalidate instead of copying max-age.
• Config.php — Removed PageCacheConfig dependency, reads caching application type directly from ScopeConfig.

[1.0.1] - 2026-02-15

Fixed

• purgePattern() wrong API endpoint — TridentClient::purgePattern() was calling /admin/purge/pattern which does not exist. Fixed to use the correct endpoint /admin/purge/urls.
• Cache tags reference table — The admin purge page showed incorrect tag patterns (product-{id}, category-{id}) instead of Magento's actual cache tags (cat_p_{id}, cat_c_{id}, cms_p_{id}, cms_b_{id}).
• PurgeAll controller redirect — Changed from hardcoded redirect path to setRefererOrBaseUrl() so users return to the page they came from.
• Null safety in CacheBlockPlugin — Added null check on getButtonList() to prevent errors when button list is not available.

Added

• Cache status bar on Cache Management page — Displays Trident cache statistics (entries, memory, hit ratio, hits, misses, purge mode) directly on Magento's System > Cache Management page.
• "Purge Trident Cache" button on Cache Management page — Adds a purge button to Magento's native cache management page with ACL permission check and confirmation dialog.
• CacheTypePlugin tag-based purge — Intercepts programmatic PageCache\Type::clean(tags) calls that bypass the clean_cache_by_tags event (e.g. from third-party extensions). Filters out Magento-internal FPC tag. This covers an invalidation path that even Magento's own Varnish module does not handle.
• PurgeStrategy for smart tag filtering — Optional optimization to filter out category listing tags (cat_c_p_{id}) for product saves where only detail-level attributes changed. Currently disabled, to be enabled via admin config after testing.

Changed

• CacheTypePlugin cleaned up — Removed logger dependency, added proper PHPDoc with FQDN types, added FPC tag filtering to prevent sending Magento-internal tags to Trident.
• FlushCacheByTagsObserver uses PurgeStrategy — Tag filtering is now applied before sending purge requests to Trident.

[1.0.0] - 2026-02-10

Added

• Initial release of Qoliber_TridentCache Magento 2 module.
• Full Page Cache integration with Trident cache server.
• Tag-based cache invalidation via FlushCacheByTagsObserver using Magento's native Tag\Resolver.
• Full cache flush via CacheFlushObserver on admin cache flush events.
• CacheTypePlugin intercepting PageCache\Type::clean() for full flush.
• ResponsePlugin ensuring s-maxage header on cacheable responses.
• ApplicationPlugin adding Trident option to cache application dropdown.
• Admin panel with cache statistics dashboard and manual purge controls.
• ACL permissions for cache purge and statistics access.
• Configurable API URL and token via Magento admin (Stores > Configuration > System > FPC).
• Sensitive config handling (API token marked as sensitive/environment).