| |
@@ -11,6 +11,13 @@
|
| |
enum:
|
| |
- container-image
|
| |
type: string
|
| |
+ registry:
|
| |
+ description:
|
| |
+ URL of the container image registry.
|
| |
+ examples:
|
| |
+ - quay.io
|
| |
+ - docker.io
|
| |
+ type: string
|
| |
repository:
|
| |
description:
|
| |
Name of the container image repository.
|
| |
@@ -60,19 +67,9 @@
|
| |
- true
|
| |
- false
|
| |
type: boolean
|
| |
- nvr:
|
| |
- description:
|
| |
- Name-version-release of the artifact.
|
| |
- examples:
|
| |
- - someapp-2.8.71-7.el7_4
|
| |
- type: string
|
| |
source:
|
| |
description:
|
| |
- The first item in the request field from task details. This is
|
| |
- usually a link to git repository with a reference, delimited with
|
| |
- the '#' sign. In case of a scratch build or other build built via
|
| |
- uploading a src.rpm the build task source will look like the bash
|
| |
- scratch build.
|
| |
+ This is usually a link to git repository with a reference, delimited with the '#' sign.
|
| |
examples:
|
| |
- git+https://github.com/docker/rootfs.git#container:docker
|
| |
type: string
|
| |
@@ -89,9 +86,8 @@
|
| |
required:
|
| |
- type
|
| |
- repository
|
| |
+ - pull_ref
|
| |
- digest
|
| |
- - issuer
|
| |
- - scratch
|
| |
- id
|
| |
|
| |
type: object
|
| |
The container-image type is meant to be a more generic type than
redhat-container-image. The redhat-container-image is supposed to represent a
container image build that we know was built in brew+OSBS, which means we can
make certain assumptions about it. The container-image type here required
the use of fields which don't make sense for a generic container-image from the
Internet. Here, I only remove the requirement to include those fields. I
think we should remove the fields in general in a separate PR, but I want to
make sure that no-one is using them first.
The pull_ref should be required, because since container-images are generic
there is no way to locate the content without it.