A shared message broker

Tower → Create → InfraService

dev exactly, as in part 1. Tower opens a PR against the tenants repo; merge it. Within a few minutes:

$ kubectl get infraservice skyport-broker -n app-skyport-broker-cicd
NAME             SYNCED   READY   COMPOSITION                    AGE
skyport-broker   True     True    infraservices.catalog.idp.io   2m

It created one repo, gitops-infra-skyport-broker, holding only a README.md and a stub cicd.yaml. There is no application to build, so there is no pipeline.

Copy the code in

git clone https://github.com/jfillman/airframe.git /tmp/airframe   # skip if you still have it
cd flight-api
A=/tmp/airframe/examples/skyport/flight-api
cp $A/pom.xml .
cp $A/src/main/resources/application.properties src/main/resources/
cp $A/src/main/java/io/skyport/flight/{FlightMessage,FlightEventPublisher,NoopFlightEventPublisher,RabbitFlightEventPublisher,FlightService}.java src/main/java/io/skyport/flight/
cp $A/src/test/java/io/skyport/flight/{FlightServiceTest,RabbitFlightEventPublisherTest}.java src/test/java/io/skyport/flight/
./test.sh                # 21 passing

Attach it, and hand it the connection details

components:
  # ... flight-db stays as it is ...
  - type: rabbitmq
    name: flight-mq            # credentials land in Secret flight-mq-user-credentials
    spec:
      mode: attach
      brokerRef: { name: skyport-broker, namespace: app-skyport-broker-dev }
      vhost: flights
      publish: [flights.events]   # may declare and publish to this exchange, nothing else

env:
  # ... the DB_* entries stay as they are ...
  - { name: EVENTS_ENABLED, value: "true" }
  - { name: RABBITMQ_HOST,     valueFrom: { configMapKeyRef: { name: flight-mq-connection, key: host } } }
  - { name: RABBITMQ_VHOST,    valueFrom: { configMapKeyRef: { name: flight-mq-connection, key: vhost } } }
  - { name: RABBITMQ_USER,     valueFrom: { secretKeyRef:    { name: flight-mq-user-credentials, key: username } } }
  - { name: RABBITMQ_PASSWORD, valueFrom: { secretKeyRef:    { name: flight-mq-user-credentials, key: password } } }

Nothing is copied through Infisical: the app reads the Secret and the ConfigMap directly with valueFrom, exactly as it reads the database's credentials in part 2. Commit both, push, and let the pipeline run; git pull before your next push, because the deploy stage commits the image into platform/envs/dev.yaml.

Copy the code in

cd boarding-api
A=/tmp/airframe/examples/skyport/boarding-api
cp $A/{app.js,index.js,events.js,store.js,package.json,package-lock.json} .
cp $A/test/{app.test.js,events.test.js} test/
npm ci && npm test        # 18 passing

Attach it

components:
  # ... the redis cache stays as it is ...
  - type: rabbitmq
    name: board-mq             # credentials land in Secret board-mq-user-credentials
    spec:
      mode: attach
      brokerRef: { name: skyport-broker, namespace: app-skyport-broker-dev }
      vhost: flights
      queuePrefix: boarding    # may create, bind and consume queues named boarding.*
      consume: [flights.events] # may bind them to this exchange, not publish to it

env:
  # ... REDIS_URL and FLIGHT_API_URL stay as they are ...
  - { name: RABBITMQ_HOST,     valueFrom: { configMapKeyRef: { name: board-mq-connection, key: host } } }
  - { name: RABBITMQ_VHOST,    valueFrom: { configMapKeyRef: { name: board-mq-connection, key: vhost } } }
  - { name: RABBITMQ_USER,     valueFrom: { secretKeyRef:    { name: board-mq-user-credentials, key: username } } }
  - { name: RABBITMQ_PASSWORD, valueFrom: { secretKeyRef:    { name: board-mq-user-credentials, key: password } } }

Commit, push, and let the pipeline redeploy.

Create the environment

Tower → Create → ApplicationEnvironment: Name skyport-broker-prod-staging, Namespace app-skyport-broker-cicd, appName skyport-broker, cluster prod, env staging, and appType infra. Merge the PR, as in part 1, section 07. Needs airframe v0.3.90. appType tells the environment its deploy repo is gitops-infra-skyport-broker, not gitops-skyport-broker; without it the values file is written to a repo that doesn't exist and the environment reports Unready resources: app-usage. Both were found when someone created this environment.

Configure it in a pull request

In the PR that adds gitops-infra-skyport-broker/prod/staging/values.yaml, use the same components: block as section 03 with allowedNamespaces: [app-flight-api-staging, app-boarding-api-staging].

Attach the apps

In each app's staging values, add its attach component and the env entries from sections 04 and 05, with brokerRef pointing at app-skyport-broker-staging.