Skip to content

CCM-17343: Add routing for supplier config data#136

Open
stevebux wants to merge 2 commits into
mainfrom
feature/CCM-17343-Route-Supplier-Config
Open

CCM-17343: Add routing for supplier config data#136
stevebux wants to merge 2 commits into
mainfrom
feature/CCM-17343-Route-Supplier-Config

Conversation

@stevebux
Copy link
Copy Markdown

Description

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@stevebux stevebux requested a review from a team as a code owner May 11, 2026 14:01
@stevebux stevebux changed the title Add routing for supplier config data CCM-17343: Add routing for supplier config data May 11, 2026
@stevebux stevebux force-pushed the feature/CCM-17343-Route-Supplier-Config branch from d042837 to 94ac39a Compare May 12, 2026 12:30
@stevebux stevebux force-pushed the feature/CCM-17343-Route-Supplier-Config branch 2 times, most recently from 55f0113 to 9785cfb Compare May 14, 2026 13:59
@stevebux stevebux requested a review from Copilot May 14, 2026 13:59
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds EventBridge routing to forward Supplier Config events from the control-plane event bus to the Supplier API SNS target, including a dedicated DLQ and required IAM role/policy wiring. Also updates the control-plane event bus ingestion policy to allow an additional principal role pattern.

Changes:

  • Add a new control-plane EventBridge rule + target to route uk.nhs.notify.supplier-config* events to the Supplier API SNS topic, with a DLQ.
  • Add a new SQS DLQ module and queue policy allowing EventBridge to send failed deliveries.
  • Expand the control-plane event bus policy’s aws:PrincipalArn allowlist to include the service-role/GitHub_Deploy role path.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
infrastructure/terraform/components/events/module_supplier_config_to_supplier_api_events_dlq.tf Introduces a new DLQ module + policy document for the new Supplier Config → Supplier API routing.
infrastructure/terraform/components/events/cloudwatch_event_rule_supplier_config_to_supplier_api.tf Adds the EventBridge rule/target and the IAM role/policy enabling publish to the Supplier API SNS topic.
infrastructure/terraform/components/events/cloudwatch_event_bus_policy_control_plane.tf Extends the control-plane event bus ingest policy allowlist to include the GitHub deploy role path.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

values = distinct(flatten([
formatlist("arn:aws:iam::%s:role/comms-*-api-event-publisher", var.event_publisher_account_ids),
formatlist("arn:aws:iam::%s:role/nhs-notify-*-eventpub", var.event_publisher_account_ids),
formatlist("arn:aws:iam::%s:role/service-role/GitHub_Deploy", var.event_publisher_account_ids),
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.

2 participants