debian-forge-composer/internal/cloudapi/v2
Achilleas Koutsou 6e4efabf24 cloudapi: use manifest content to resolve containers
Use the container sources provided by the content on the initialised
manifest instead of the blueprint to resolve containers.  The container
sources on the manifest are a map keyed by the name of the pipeline that
will use the resolved containers, but the worker's container resolve job
works on a slice, so we reread the content map to get the pipeline name
(instead of taking the first payload pipeline from the image type).
This requires that there be only one pipeline that embeds containers,
which currently true of all our image types.
2023-06-14 11:19:29 +02:00
..
errors.go Cloud API: add error for failed customization validation 2023-02-22 12:17:36 +01:00
errors_test.go cloudapi: get specific error from openapi 2022-06-28 10:02:55 +02:00
handler.go cloudapi: add vsphere-ova type 2023-06-05 11:22:07 +02:00
middleware.go cloudapi: get specific error from openapi 2022-06-28 10:02:55 +02:00
openapi.v2.gen.go cloudapi: add vsphere-ova type 2023-06-05 11:22:07 +02:00
openapi.v2.yml cloudapi: add vsphere-ova type 2023-06-05 11:22:07 +02:00
server.go cloudapi: use manifest content to resolve containers 2023-06-14 11:19:29 +02:00
v2_internal_test.go internal/rpmmd: change ignoressl to pointer 2023-05-31 16:24:36 +02:00
v2_koji_test.go Make Manifest() return manifest.Manifest 2023-05-31 16:40:07 +02:00
v2_multi_tenancy_test.go cloudapi: Correctly test dependency errors 2022-08-03 13:51:52 +02:00
v2_test.go Make Manifest() return manifest.Manifest 2023-05-31 16:40:07 +02:00