Manage Ssp Feature Deployment
Queues an asynchronous deployment workflow for one platform feature, for example Security Intelligence.
Actions:
RUN_PRECHECK: Run pre-flight validation checks against the feature configurationDEPLOY: Execute pre-flight validation checks and deploy the feature using the staged configurationUNDEPLOY: Remove the deployed feature (fails if dependencies exist)FORCE_UNDEPLOY: Forcefully remove the deployed feature and cascade delete dependencies
Chain: Asynchronous Polling: To monitor the progress of a feature operation, poll GET /lcm/features/{feature}/status. Ongoing operations return a 202 Accepted response formatted as an AsyncApiResponse. Clients should retain the response id for activity correlation and continue polling the provided status_url until the operation concludes.
Notes:
- Do not treat a '202' Accepted status as a completed operation. It strictly indicates that the background task has been queued and requires subsequent polling.
- Concurrency conflicts yield a '412' status. Resolve this by fetching the latest resource, merging your payload updates, and submitting a new request with the updated _revision token.
See Endpoint Guide for route comparison and workflow.
Platform feature key to manage. Values are case-sensitive and listed in the SspFeature schema.
For example INTELLIGENCE corresponds to Security Intelligence.
Deployment command body: required _revision from GET, plus action. Named examples include sample payloads.
{
"_create_user": "string",
"_create_time": 0,
"_last_modified_user": "string",
"_last_modified_time": 0,
"_revision": 0,
"_resource_type": "string",
"_system_owned": false,
"id": "string",
"display_name": "string",
"description": "string",
"site_ids": [
"string"
],
"action": "string"
}
The deployment action has been successfully queued for background processing. To monitor the live execution state, poll GET /lcm/features/{feature}/status. Clients should extract and retain any asynchronous identifiers provided in the response envelope to correlate with system activity logs.
{
"id": "8f7e7db8-9c4a-4f2e-a501-7c4f8d6e2b11",
"status_url": "/ssp/lcm/features/INTELLIGENCE/status"
}
UUID identifier of the response.
The URL to check the status of the operation.
Bad Request
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Unauthorized
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Forbidden
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Failed
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Required
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Too Many Requests
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
An error occurred while processing the request. This could be due to authentication issues, authorization failures, invalid requests, precondition failures (such as revision mismatch), or internal server errors.
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
curl -X PUT -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"action":"string","_revision":"{}"}' https://{api_host}/ssp/lcm/features/{feature}