Update DPU Extension Service
Update a specific DPU Extension Service.
DPU Extension Service must be owned by current Tenant. A new version will be created if data or credentials are modified.
For a DpfHelmChart service, credentials and observability are unsupported, and data is accepted only while the service is Ready and only when it differs from the current definition.
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix.
Authentication
export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current
Path parameters
Request
Credentials to download resources specified in DPU Extension Service data; unsupported for DpfHelmChart
Observability configuration for the DPU Extension Service version; unsupported for DpfHelmChart
Response
Immutable deployment policy. Omitted or null on create defaults to DemandDriven,
which deploys through instance attachment. Baseline is supported only for
DpfHelmChart services and requests deployment to all DPUs managed by DPF at
creation, without a DPU target. Baseline services cannot be attached to instances.
Empty and unknown values are rejected. Responses always include the stored policy.
This field cannot be changed through updates.
Immutable host-scoped placement for DemandDriven Helm services; null for Baseline Helm and KubernetesPod services
Date/time when the DPU Extension Service was created
Date/time when the DPU Extension Service was last updated