Skip to content

Scott/chart drop meilisearch - #243

Merged
binaryknot merged 1 commit into
lago-v2from
scott/chart-drop-meilisearch
Sep 1, 2026
Merged

Scott/chart drop meilisearch#243
binaryknot merged 1 commit into
lago-v2from
scott/chart-drop-meilisearch

Conversation

@binaryknot

Copy link
Copy Markdown
Contributor

Remove Meilisearch from the lago chart

Meilisearch is fully decommissioned across Lago (workers, server, PVCs, IAM, DNS, Zitadel OIDC — all torn down) and removed from lago-infrastructure and lago-deploy. This strips the last of it from the chart, including the global.meilisearch env-projection integration wired through the config and rails subcharts.

Changes

  • lago-config — drop the meilisearch.endpoint ConfigMap key and meilisearch.apiKey Secret key, plus the global.meilisearch values block.
  • lago-rails — drop the LAGO_MEILISEARCH_URL / LAGO_MEILISEARCH_SEARCH_ENABLED / LAGO_MEILISEARCH_API_KEY env projection, the global.meilisearch values block, and the meilisearch_search_enabled unit test.
  • lago-pdf — drop the global.meilisearch values block.
  • lago (umbrella) — drop the meilisearch-worker dependency (Chart.yaml + Chart.lock), the sidekiq.queues.meilisearch toggle, the global.meilisearch block, the meilisearch-worker overrides, and the README references.

Validation

helm lint passes. Unit tests pass: 63 in lago-config/lago-rails, 61 in the umbrella chart (deps rebuilt). Templates render with zero Meilisearch references and no nil-pointer, including with global.sidekiq.queues.meilisearch=true forced. Template consumers and their values were removed together so absent global.meilisearch can't error.

Chart version bump is left to the standard lockstep release chore (mirroring how the worker was originally added).

@binaryknot
binaryknot requested a review from koikonom September 1, 2026 17:05
@binaryknot
binaryknot changed the base branch from main to lago-v2 September 1, 2026 17:06
@binaryknot
binaryknot merged commit 39133e6 into lago-v2 Sep 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants