Create Container Registry
Once you have fetched your required information, you can now create a new registry. For the registry, you can alter the days and time. You can also update the location based on the available container registry locations.
We assume the following prerequisites:
With the POST
request, you can create a container registry.
Request
Input Parameters
You can update the limit value to get specific registries based on the limit value being passed.
Field | Type | Description | Example |
---|---|---|---|
days | array | The days of the week selected. |
|
time | string | The timestamp of creation of the registry |
|
location | string | The location of the resource. |
|
name | string | The name of the registry. It must be unique within the folder. |
|
days | array | The days of the week selected. |
|
apiSubnetAllowList | array | The list of IP subnets that can access the registry. If this parameter is omitted, the registry will be accessible from any IP address. |
|
Response
200 OK - Successfully showed the list of registries
Response Fields
Field | Type | Description | Example |
---|---|---|---|
id | string | The ID of fetched output. |
|
type | string | The type of resource. |
|
createdBy | string | ID of the user or service account that initiated the operation. |
|
createdDate | string | The date when the operation was initiated. |
|
days | array | The days of the week selected. |
|
apiSubnetAllowList | array | The list of IP subnets, in CIDR notation, that can access the registry. For single IPs a |
|
Note:
Your values will differ from those in the sample code. The container registry will be created as shown in the 201 response. Your response will have a different
id
,createdBy
andcreatedDate
.Here, we do not get a hostname in the output because the host has not be allocated yet.
400 Bad Request - The request made is invalid or corrupted
Last updated