chore: Remove meilisearch - #242
Closed
binaryknot wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove Meilisearch from the lago chart
Meilisearch has been fully decommissioned across Lago infra (workers, server, PVCs, IAM, DNS, Zitadel OIDC — all torn down) and stripped from lago-infrastructure and lago-deploy. This removes the last of it: the dormant Meilisearch worker in the chart itself.
Changes
Chart.yaml— drop themeilisearch-workerdependency (lago-rails alias gated onglobal.sidekiq.queues.meilisearch).values.yaml— drop thesidekiq.queues.meilisearchtoggle and themeilisearch-workersubchart overrides block.README.md— drop the dependency-table row and the Meilisearch Worker section.Validation
helm lintpasses with 0 failures.helm templaterenders zero Meilisearch references — including whenglobal.sidekiq.queues.meilisearch=trueis forced, confirming the subchart is gone and can't bere-enabled by a stale value. The other 11 worker subcharts are unaffected.
Chart version bump is left to the standard lockstep release chore (mirroring how the worker was originally added).