Skip to content

ci: grant id-token: write for Slack notify workflow - #255

Merged
hln33 merged 1 commit into
mainfrom
fix/notify-id-token-permission
Aug 21, 2026
Merged

ci: grant id-token: write for Slack notify workflow#255
hln33 merged 1 commit into
mainfrom
fix/notify-id-token-permission

Conversation

@hln33

@hln33 hln33 commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Fixes aws/aws-durable-execution-ci#30.

The reusable notify.yml in aws-durable-execution-ci changed its
summarize job at ac55d9f to assume BEDROCK_ROLE_ARN via OIDC,
requiring id-token: write. Consumer notify.yml files still grant
only contents: read + models: read, and GitHub caps a reusable
workflow's token at the caller's grant — aborting the run at startup
and dropping all Slack notifications.

Changes (identical across all four consumer repos):

  • Add id-token: write permission
  • Explicitly forward BEDROCK_ROLE_ARN (enables AI-generated summaries
    when the org secret is configured) alongside the existing Slack webhooks

@hln33
hln33 merged commit fa0c50c into main Aug 21, 2026
7 of 9 checks 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.

Broken Slack notification workflow

2 participants