feat: add cloudly appstore worker scenario
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
# onebox-cloudly-appstore-worker
|
||||
|
||||
This full scenario verifies the Onebox-to-Cloudly app-store path and the worker bootstrap endpoint exposed by the installed Cloudly service.
|
||||
|
||||
Assertions:
|
||||
|
||||
- Onebox starts from an isolated bare working directory in dev mode.
|
||||
- The remote app-store catalog exposes the Cloudly template.
|
||||
- Installing Cloudly from the template provisions MongoDB and MinIO platform resources.
|
||||
- Cloudly starts as a Onebox-managed Docker service with the template version tracked on the service record.
|
||||
- Onebox ingress routes HTTP traffic to the installed Cloudly service.
|
||||
- Cloudly exposes `/curlfresh/setup.sh`, which is the current worker-node bootstrap script used by freshly provisioned nodes.
|
||||
|
||||
Run with:
|
||||
|
||||
```bash
|
||||
pnpm scenario:onebox-cloudly-appstore-worker
|
||||
```
|
||||
|
||||
This scenario is intentionally excluded from the default `pnpm test` because it pulls and starts the Cloudly image plus platform services.
|
||||
Reference in New Issue
Block a user