Value Statement

Understand the features of pubsub can provide

Definition of Done for Engineering Story Owner (Checklist)

• Make a prototype via https://cloud.google.com/pubsub/docs/publish-receive-messages-client-library
• understand the topic and subscriptions. Can we configure topic likes sources//clusters//agentevents ?
• How to do access control for topic?
• How does filter subscription work? does it work with multiple maestro agents and servers?
• Payload and attributes (work with filter subscription) for cloudevents-sdk-go: https://github.com/cloudevents/sdk-go/tree/main/protocol/pubsub/v2
• what happen when Google PubSub service account token expires? How to rotate it, does client auto reload the refresh token? What happens to client when token expires?

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_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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