Add backbeat route apis #4
Conversation
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
13 times, most recently
from
5305e7d to
670da80
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-7
branch
16 times, most recently
from
51e8e9c to
3d0f040
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-7
branch
from
3d0f040 to
e09c5a5
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
5 times, most recently
from
9ffcbce to
0ad1669
Compare
.github/docker-compose.yml
Outdated
| # MongoDB (base) | ||
| # =================== | ||
| mongodb: | ||
| image: mongo:5.0 |
There was a problem hiding this comment.
some parameters (mongodb image/version, port...) are duplicated : should probably be moved to an .env file to ensure consistency
.github/docker-compose.yml
Outdated
| # =================== | ||
| # Cloudserver with MongoDB + Backbeat | ||
| # =================== | ||
| cloudserver-backbeat: |
There was a problem hiding this comment.
why not merge this with the cloudserver service?
(just need to drop the dependency on 'backbeat' if we want to be able to start it without all the backbeat/zookeeper/... stack)
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
3 times, most recently
from
d7986fe to
5b20462
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
5 times, most recently
from
04d210b to
b346637
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
from
b346637 to
a3b3666
Compare
| - name: Stop Cloudserver | ||
| if: always() | ||
| run: docker compose -f .github/docker-compose.cloudserver-mongo.yml down | ||
| run: docker compose -f .github/docker-compose.yml --env-file .github/docker.env --profile mongo down |
There was a problem hiding this comment.
is this needed? the runner will be destroyed anyway...
| import { describeForBackbeatSetup } from './testHelpers'; | ||
| import assert from 'assert'; | ||
|
|
||
| // Note : these tests are relatively simple, as it's not straightforward to setup |
There was a problem hiding this comment.
note for thought (nothing to change now!) : instead of deploying "full" services (and thus having some sort of integration tests), we could have "mocked" the API in the tests (kind of more "unit test" approach, which avoids depending on the external packages & setting up all services)
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
from
a3b3666 to
00b92a5
Compare
SylvainSenechal
force-pushed
the
improvement/CLDSRVCLT-5
branch
from
00b92a5 to
18472a8
Compare
ISSUE: CLDSRVCLT-5