Skip to content

Add workflow to notify consumers when images publish - #109

Merged
TonyCTHsu merged 8 commits into
mainfrom
feature/notify-dd-trace-rb
Aug 5, 2026
Merged

Add workflow to notify consumers when images publish#109
TonyCTHsu merged 8 commits into
mainfrom
feature/notify-dd-trace-rb

Conversation

@TonyCTHsu

@TonyCTHsu TonyCTHsu commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds notify-consumers.yml: after a successful Main build on main, it notifies downstream repos that pin images-rb images (via repository_dispatch) so they can update their pins. Fans out to a matrix of consumers — currently just dd-trace-rb — and guards against a manual re-trigger racing ahead of the image build.

Verification

Reviewed by hand; no automated tests. End-to-end verification is pending the cross-repo dd-octo-sts grant to dd-trace-rb.

Matches the corresponding simplification on the dd-trace-rb side;
previewing unmerged images-rb changes is no longer in scope.
…-out

Split the single notify job into determine-inputs (unchanged
trigger-gating logic) feeding a matrixed notify job, so publishing an
image-updated event to additional consumer repos is a matrix entry
away. fail-fast: false isolates a failed dispatch to one consumer from
blocking delivery to the others. Only DataDog/dd-trace-rb is wired up
for now; other consumers (e.g. system-tests) are deliberately not
added yet.
Marks system-tests as a known future consumer without wiring it up:
no receiver workflow or dd-octo-sts grant exists for it yet.
Keep a single explanatory block above the commented-out entry instead
of a duplicated comment above both matrix items.
Replaces the system-tests-specific placeholder with a generic
checklist: matrix entry, consumer-side dd-octo-sts policy, cross-repo
grant, and a receiver workflow, since all four are prerequisites for
any new consumer, not just system-tests.
The comment describes the whole workflow's trigger behavior, not just
determine-inputs, so it belongs at the top of the file alongside the
manual re-trigger note.
A manual workflow_dispatch can be run against any ref at any time,
including a feature branch commit whose Main build hasn't finished
publishing an image yet. Query the Actions API for the most recent
completed Main run at that commit and fail loudly if it didn't
succeed, before notifying any consumer.
@TonyCTHsu
TonyCTHsu requested a review from a team as a code owner August 4, 2026 10:37

@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: 8b1f7629e9

ℹ️ 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".

Comment thread .github/workflows/notify-consumers.yml
@eregon

eregon commented Aug 5, 2026

Copy link
Copy Markdown
Member

This works but is maybe overly complex?
What I'm thinking in since there will be some delay anyway (building the images, the sleep 30), maybe it could just be a daily cron job in dd-trace-rb + manual workflow_dispatch when one wants to be faster.
But, I think this should be nice when making a PR to this repo as then the rest is automated, so 👍

@TonyCTHsu
TonyCTHsu merged commit 224f5e3 into main Aug 5, 2026
372 of 373 checks passed
@TonyCTHsu
TonyCTHsu deleted the feature/notify-dd-trace-rb branch August 5, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants