Skip to content

M3b: Azure configuration for the M3a features (Redis, inventory address, signing key) #6

Closed

Description

@MAOFILHO

What to build

The M3a features work in Azure the way they work under make run:

  • An event bus: a Redis Container App with internal-only ingress and one replica while provisioned. Order and inventory get its address, so the outbox drains and inventory finishes sales.
  • The order service can reach inventory, so the saga's stock-hold step works. Today its Azure settings only know user, catalog and payment.
  • The user service signs login tokens with a key that make provision generates once and stores as a Container Apps secret, so restarts and scale-out do not log anyone out. The key never goes to git or to logs.
  • Demo switches stay off in Azure.

No Azure spend in this ticket: verified by compiling the templates and by unit tests. The real run is a later ticket.

Acceptance criteria

  • Redis is defined with internal ingress only (not reachable from the internet).
  • Order and inventory receive the bus address; order receives the inventory address.
  • The signing key is generated by provision, passed as a secret, and redacted from command output.
  • Bicep compiles in CI; unit tests cover key generation and redaction.
  • Estimated extra cost per 8-hour session stays under $0.10 (documented in cost_estimate.md).
  • Built test-first (implement skill), then reviewed with the code-review skill.

Blocked by

None (can start immediately).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions