Send the SDK release dispatch to every repository listening for it - #1320
Send the SDK release dispatch to every repository listening for it#1320BeArchiTek wants to merge 1 commit into
Conversation
Deploying infrahub-sdk-python with
|
| Latest commit: |
b341679
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://46219293.infrahub-sdk-python.pages.dev |
| Branch Preview URL: | https://ci-reconcile-sdk-dispatch-ta.infrahub-sdk-python.pages.dev |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## stable #1320 +/- ##
==========================================
- Coverage 84.24% 84.24% -0.01%
==========================================
Files 147 147
Lines 13068 13047 -21
Branches 1940 1930 -10
==========================================
- Hits 11009 10991 -18
+ Misses 1494 1493 -1
+ Partials 565 563 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Closing this unmerged, for the same reason as its companion opsmill/infrahub#10510: the dispatch system is being replaced with bot-triggered fan-out, which engineering is piloting, so hand-reconciling the matrix would be thrown-away work. Recording the survey so the replacement does not have to redo it. As of 2026-09-03, these repositories carry an
Two of eleven wired. The That case is also the argument for not rebuilding this as two hand-maintained lists: the drift runs in both directions and is silent either way. A listener with no sender never fires; a sender with no listener dispatches into the void. Deriving one side from the other would remove the whole class. |
The matrix names four recipients. Eleven repositories carry an
`on: repository_dispatch: types: [trigger-infrahub-sdk-python-update]`
listener, and only two of them are wired: infrahub-demo-dc and infrahub-sync.
The other nine have bump workflows that have never been triggered.
The reverse case is here too. opsmill/emma is dispatched to on every release
and has no listener for this event at all, so the dispatch is accepted and
consumed by nothing. infrahub-github-bot/config.yaml already records this
("emma is deliberately absent: it is dispatched to today but has no listener")
but this matrix was never corrected to match. Left in place rather than
removed, because whether emma should gain a listener or lose the dispatch is
its owner's call.
infrahub-demo-otn's listener is in flight and lands before this is useful to
it; a dispatch to a repository with no matching listener is a no-op, so the
ordering is safe either way.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ab6399e to
b341679
Compare
|
Correction: disregard my previous comment and the close. I misread the instruction. The matrix additions are wanted; what was asked for was dropping the drift-detection tooling, not the reconciliation itself. Reopened, and the branch now carries only the added repositories. Removed since the earlier review:
The branch was force-pushed to amend the single commit rather than stack a revert on top, because the original commit message described the query that no longer exists. Longer term this is superseded by bot-triggered fan-out, which engineering is piloting. This PR is the interim step that gets the six unwired repositories receiving release notifications in the meantime. |
1 participant
Summary
When the SDK publishes a release, this workflow tells downstream repositories so they can open their own version-bump pull request. The matrix names four recipients. Eleven repositories carry a listener for
trigger-infrahub-sdk-python-update, and only two of them are wired —infrahub-demo-dcandinfrahub-sync. The other nine have bump workflows that have never once been triggered.This adds the nine missing recipients, and flags one dispatch that goes nowhere.
Key Changes
Added to the matrix:
opsmill/infrahub-ansibleopsmill/infrahub-arista-avdopsmill/infrahub-demo-otnopsmill/infrahub-demo-service-catalogopsmill/infrahub-demo-spopsmill/infrahub-mcpopsmill/infrahub-solution-ai-dcopsmill/infrahub-sync-labopsmill/nornir-infrahubOne decision left for an owner:
opsmill/emmaemmais dispatched to on every SDK release and has no listener for this event at all, so the dispatch is accepted and consumed by nothing.Related
Companion PR for the Infrahub-side matrix, which had the same defect: opsmill/infrahub#10510.
opsmill/infrahub-demo-otn's listener for this event is in flight and lands before this is useful to it. A dispatch to a repository with no matching listener is a no-op rather than an error, so the ordering is safe either way.Base branch
Targeted at
stablerather thandevelopon purpose:release.ymlfires onrelease: published, so the file that executes is the one at the release tag, and the bot already syncsstableintodevelop. Please correct me if that is wrong for this repo — recent PRs here are split acrossdevelop,infrahub-developandstable, so I reasoned it from the release trigger rather than from convention.Test Plan
Nothing to run: the change is a matrix list. Verification is on the next SDK release, where each newly added repository should show a run of its own bump workflow shortly after the release publishes.
Summary by cubic
Wires the SDK release dispatch to every repository listening for it. Only two of eleven listener repositories were wired before, so nine version-bump workflows never ran.
opsmill/emmain the matrix; its dispatch is a no-op, and whether it gains a listener or loses the dispatch is its owner's call.Written for commit b341679. Summary will update on new commits.