mirror of
https://github.com/docker/compose.git
synced 2026-10-12 10:59:50 +00:00
Nicolas De Loof
3a5353d4ec
The remote loaders had almost no end-to-end coverage: one test consumed an OCI artifact (config only, plus an up declined at the prompt) and nothing exercised the git loader at all. Git scenarios run against a throwaway repository served over the smart HTTP protocol by an in-process server — git http-backend as a CGI per httptest request: no daemon, no container, no fixed port. Smart HTTP is a hard requirement: the loader ls-remotes the ref then shallow-fetches the raw commit, which the dumb protocol cannot serve (no shallow capability) and which needs uploadpack.allowAnySHA1InWant. Covered: deploying from the default branch with repository-relative files, selecting a #branch, selecting a #ref:subdir project. OCI scenarios publish the fixture to a throwaway local registry (the TestPublish pattern) then deploy from oci://: a full up consuming the bundled env-file layer, and tag selection between two published revisions. Signed-off-by: Nicolas De Loof <[email protected]>
8 lines
110 B
YAML
8 lines
110 B
YAML
services:
|
|
app:
|
|
image: alpine
|
|
init: true
|
|
command: sleep infinity
|
|
env_file:
|
|
- ./app.env
|