1723e588ce
Before, this was done in the PackageSets() function. The reason for this is that having an ostree ref affects package selection (for example, it adds rpm-ostree). At the package selection phase, it doesn't matter what the ostree ref is; it is just used to determine if a pipeline is for an ostree-based image type and it doesn't affect non-ostree-based image types because the image functions ignore it. This is only needed in the cloudapi now because other places have switched to using the new order of operations, where the manifest is generated after the ostree commit is resolved, so it's always added when needed. |
||
|---|---|---|
| .. | ||
| errors.go | ||
| errors_test.go | ||
| handler.go | ||
| middleware.go | ||
| openapi.v2.gen.go | ||
| openapi.v2.yml | ||
| server.go | ||
| v2_internal_test.go | ||
| v2_koji_test.go | ||
| v2_multi_tenancy_test.go | ||
| v2_test.go | ||