Deploying Configuration Changes
Although POST, PUT, and DELETE calls directly update the threat defense device, they are not immediately active. You must deploy configuration changes before the device uses your new settings when processing traffic.
Procedure
Step 1 |
Use the POST /operational/deploy resource in the Deployment group to initiate a deployment. For example, the curl command would look like the following:
|
||
Step 2 |
Evaluate the response to verify that the deployment job was queued. A good response (status code 200) looks like the following. Note the state.
|
||
Step 3 |
Use the GET /operational/deploy/{objId} resource to check the status of the job. For example, the curl command would look like the following:
The response might look like the following. Note the state, DEPLOYED, indicates the job completed successfully. The modifiedObjects parameter lists the objects that were changed in the deployment job. In this case, there is a single change, to a network object named new-network.
|