1berry/docker-compose
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
5,246 Commits 20 Branches 275 Tags
Commit Graph

23 Commits

Author SHA1 Message Date
Guillaume Lours
55b5f233c2 use Defang secret-detector to identify potential secret leaks before publishing OCI artifacts 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2025-03-11 15:02:37 +01:00
Nicolas De Loof
c3a0c35681 implement extends.file replace without yqlib 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2025-03-11 14:18:41 +01:00
Nicolas De Loof
66a47169d5 Publish compose file with required siblings used by extends 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2025-03-07 13:58:10 +01:00
Nicolas De Loof
4c2ecb542f reject compose file with bind mounts 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2025-03-04 16:10:53 +01:00
Guillaume Lours
66dfa7d181 block the publication of an OCI artifact if one or more services contain only a build section 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2025-03-03 16:23:21 +01:00
Guillaume Lours
806ac91cf6 add warning when trying to publish env variables with OCI artifact 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2025-01-30 17:37:07 +01:00
Guillaume Lours
840288895e add --with-env flag to publish command 
this flag allow publishing env variables in the Compose OCI artifact

Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2025-01-29 15:45:00 +01:00
Guillaume Lours
26064d4b60 allow usage of -f flag with oci Compose artifact 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2024-10-25 17:36:04 +02:00
Alex Bedo
cc09f39f29 Readd event 
Signed-off-by: Alex Bedo <alex98hun@gmail.com>
 2024-06-10 12:06:30 +02:00
Alex Bedo
918b508bd5 remove unreachable code 
if statement is preceded by another that has the same condition and ends with a return

Signed-off-by: Alex Bedo <alex98hun@gmail.com>
 2024-06-10 12:06:30 +02:00
Nicolas De Loof
1680f9a874 restore support for config --no-interpolate 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2024-02-28 18:54:43 +01:00
Guillaume Lours
5d05df6e5c update compose-go to version using immutable Project functions 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2024-01-11 10:44:42 +01:00
Nicolas De Loof
cda04f288e adopt compose-go/v2 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-12-05 18:54:31 +01:00
Milas Bowman
07df9cc46e fix typo 
Signed-off-by: Milas Bowman <milas.bowman@docker.com>
 2023-12-05 18:08:38 +01:00
Milas Bowman
7c8ff36d78 move around OCI logic, auto fallback/retry 1.1 -> 1.0 
Signed-off-by: Milas Bowman <milas.bowman@docker.com>
 2023-12-05 18:08:38 +01:00
Milas Bowman
111ad3b039 fix(publish): add OCI 1.0 fallback support for AWS ECR 
Currently, we publish Compose artifacts following the OCI 1.1
specification, which is still in the RC state.

As a result, not all registries support it yet. Most notably,
AWS ECR will reject certain OCI 1.1-compliant requests with
`405 Method Not Supported` with cryptic `Invalid JSON` errors.

This adds initial support for Compose to generate either an
OCI 1.0 or OCI 1.1 compatible manifest. Notably, the OCI 1.0
manifest will be missing the `application/vnd.docker.compose.project`
artifact type, as that does not exist in that version of the
spec. (Less importantly, it uses an empty `ImageConfig`
instead of the newer `application/vnd.oci.empty.v1+json` media
type for the config.)

Currently, this is not exposed as an option (via CLI flags or
env vars). By default, OCI 1.1 is used unless the registry
domain is `amazonaws.com`, which indicates an ECR registry, so
Compose will instead use OCI 1.0.

Moving forward, we should decide how much we want to expose/
support different OCI versions and investigate if there's a
more generic way to feature probe the registry to avoid
maintaining a hardcoded list of domains, which is both tedious
and insufficient.

Signed-off-by: Milas Bowman <milas.bowman@docker.com>
 2023-12-05 18:08:38 +01:00
Nicolas De Loof
6727908803 introduce --resolve-image-digests for publish to seal service images by digest 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-11-02 10:43:45 +01:00
Nicolas De Loof
39008c539c align with OCI artifact best practices 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-10-23 20:26:13 +02:00
Guillaume Lours
2c0b023273 add dry-run support for publish command 
Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
 2023-10-05 21:55:00 +02:00
Bjorn Neergaard
12e0ac898a pkg/compose/publish: use empty config descriptor mediaType 
Signed-off-by: Bjorn Neergaard <bjorn.neergaard@docker.com>
 2023-09-29 05:27:14 +02:00
Nicolas De Loof
5ca35c88be implement publish 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-09-20 18:14:58 +02:00
Nicolas De Loof
e0f39ebbef pull OCI remote resource 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-09-07 07:27:32 +02:00
Nicolas De Loof
c9d54f09cf introduce publish (alpha) command 
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
 2023-09-07 07:27:32 +02:00