9523172280
69%

Ran 14 Jun 2024 10:40PM UTC

Jobs 1

Files 122

Run time 1min

Badge

Embed ▾

Committed 14 Jun 2024 10:36PM UTC coverage: 56.362% (-0.04%) from 56.405%

Build # 9523172280

Build Type

push

github

Committed by

web-flow

Commit Message

compose.yaml: autopair first-party leader (#1099)

To enable the demo workflow, users will need to pair two aggregators
with the control plane. Further, one of them must be first-party, which
can only be done using a CLI built with feature `admin`. But the one we
distribute via GitHub releases isn't, and I argue it shouldn't be, which
means that demo users can't appropriately pair aggregators.

We could provide a `curl` or `wget` command that'd do it, but as it
turns out, we already bundle the `divviup` CLI in the `divviup_api`
container, so let's just use that, since the API URL and token for the
aggregators are static!

I'm thinking we should have the demo user pair the other aggregator
themselves with `divviup` to simulate what they might have to do in a
realistic use case, if they bring their own helper.

Building on previous changes, this commit moves the `pair_aggregator`
service into the main `compose.yaml`, leaving `build` and `develop`
stanzas for it in `compose.dev.override.yaml`. Additionally, the
`divviup_api_integration_test` image version is bumped to one built with
feature `admin`, which should get the tests working.

Part of #1096

Coverage Stats

3938 of 6987 relevant lines covered (56.36%)

106.86 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	9523172280.1	14 Jun 2024 10:39PM UTC	0	56.36	GitHub Action Run

Source Files on build 9523172280

Detailed source file information is not available for this build.

divviup / divviup-api / 9523172280
69%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9523172280

divviup / divviup-api / 9523172280 69%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 9523172280

divviup / divviup-api / 9523172280
69%

README BADGES
x