Update a Config Run in API Explorer
Query parameters
-
The version number of the config object being updated. This is required to avoid conflicting writes.
Body
The spec of the config to update. Currently, only the Labels field can be updated. All other fields must remain unchanged from the ConfigInspect endpoint response values.
-
User-defined name of the config.
-
User-defined key/value metadata.
-
Data is the data to store as a config, formatted as a Base64-url-safe-encoded (RFC 4648) string. The maximum allowed size is 1000KB, as defined in MaxConfigSize.
-
Name of the secrets driver used to fetch the secret's value from an external secret store.
POST
/configs/{id}/update
curl \
--request POST 'http://api.example.com/v1.49/configs/{id}/update?version=42' \
--header "Content-Type: application/json" \
--data '{"Name":"string","Labels":{"additionalProperty1":"string","additionalProperty2":"string"},"Data":"string","Templating":{"Name":"some-driver","Options":{"OptionA":"value for driver-specific option A","OptionB":"value for driver-specific option B"}}}'
Request examples
{
"Name": "string",
"Labels": {
"additionalProperty1": "string",
"additionalProperty2": "string"
},
"Data": "string",
"Templating": {
"Name": "some-driver",
"Options": {
"OptionA": "value for driver-specific option A",
"OptionB": "value for driver-specific option B"
}
}
}
Response examples (400)
{
"message": "Something went wrong."
}
Response examples (400)
{
"message": "Something went wrong."
}
Response examples (404)
{
"message": "Something went wrong."
}
Response examples (404)
{
"message": "Something went wrong."
}
Response examples (500)
{
"message": "Something went wrong."
}
Response examples (500)
{
"message": "Something went wrong."
}
Response examples (503)
{
"message": "Something went wrong."
}
Response examples (503)
{
"message": "Something went wrong."
}