Value Statement

To ensure Maestro functions correctly when using the PubSub driver, we need to add a full end-to-end (e2e) test scenario. This test should verify message publishing, delivery, and handling through Maestro using the PubSub driver, and validate that the workflow behaves consistently with other supported message brokers.

Definition of Done for Engineering Story Owner (Checklist)

• Stand up the Maestro test environment with the PubSub driver enabled using a PubSub test server.

• Run the existing e2e test suite against the PubSub server.

• Add configuration options to switch the e2e environment to use the PubSub driver (similar to gRPC/MQTT).

• Update documentation for running PubSub e2e tests locally.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.