Skip to content

chore(ee-pre-flight-checks): bump tackle to v0.4.1 - #1171

Open
loadez wants to merge 4 commits into
mainfrom
bump/tackle-v0.4.0-ee-pre-flight-checks
Open

loadez wants to merge 4 commits into
mainfrom
bump/tackle-v0.4.0-ee-pre-flight-checks

Conversation

@loadez

@loadez loadez commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@github-project-automation github-project-automation Bot moved this to Backlog in Roadmap Aug 13, 2026
@loadez
loadez marked this pull request as ready for review August 18, 2026 18:27

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 059ffde33f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

use Tackle.Multiconsumer,
url: Application.get_env(:pre_flight_checks, :amqp_url),
service: "pre_flight_checks_hub",
service_per_exchange: true,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the old queue when switching queue names

Setting service_per_exchange: true moves these consumers away from the existing pre_flight_checks_hub.deleted queue, but nothing deletes or unbinds that old queue. On the rolling deployment configured for this service, the old and new pods temporarily consume differently named queues bound to the same exchanges, so deletion events are delivered twice; after the old pod exits, its non-auto-delete queue remains bound and accumulates every subsequent deletion event without a consumer. Add an explicit queue migration/cleanup for pre_flight_checks_hub.deleted as part of this rollout.

Useful? React with 👍 / 👎.

adbatista
adbatista previously approved these changes Aug 18, 2026
@loadez
loadez force-pushed the bump/tackle-v0.4.0-ee-pre-flight-checks branch from 059ffde to baa2055 Compare August 26, 2026 11:22
@loadez
loadez force-pushed the bump/tackle-v0.4.0-ee-pre-flight-checks branch from baa2055 to 77a42ed Compare September 9, 2026 15:33
@adbatista adbatista changed the title chore(ee-pre-flight-checks): bump tackle to v0.4.0 chore(ee-pre-flight-checks): bump tackle to v0.4.1 Sep 11, 2026
tackle 0.4+ derives the queue name from service+routing_key by default.
Both routes here (organization_exchange and project_exchange) use the
same "deleted" routing key, so without service_per_exchange: true they
collapsed onto one shared queue and the two consumers competed for
deliveries, misrouting organization/project deletion events between
handlers. This is what broke CleanupConsumerTest under the tackle bump.
@loadez
loadez force-pushed the bump/tackle-v0.4.0-ee-pre-flight-checks branch from 82eef46 to 64f34f6 Compare September 14, 2026 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants