Configuration
Configuration in API v3: apply a configuration plan, create a configuration plan, validate a configuration manifest.
3 operations.
| Operation | Summary |
|---|---|
POST /configuration/applications | Apply a configuration plan |
POST /configuration/plans | Create a configuration plan |
POST /configuration/validations | Validate a configuration manifest |
Custom code
Previous Page
Apply a configuration plan POST
Applies a configuration plan previously returned by the plan operation. Submit the plan's `id` as `plan_id`, together with its `signature` and `steps`. Before accepting the request, the API verifies that the plan is still valid, that its signature matches the submitted steps, and that none of the affected resources has changed since the plan was calculated. A plan can only be applied with the same credentials used to create it, and only once. The plan is applied asynchronously. The response returns an operation, and the `Location` header points to it so you can track progress. Steps are not applied as a single transaction: if a step fails, steps that were already applied remain in effect.