> ## Documentation Index > Fetch the complete documentation index at: https://docs.eorion.com/llms.txt > Use this file to discover all available pages before exploring further. # 重新部署 > Re-deploys an existing deployment. The deployment resources to re-deploy can be restricted by using the properties `resourceIds` or `resourceNames`. If no deployment resources to re-deploy are passed then all existing resources of the given deployment are re-deployed. **Warning**: Deployments can contain custom code in form of scripts or EL expressions to customize process behavior. This may be abused for remote execution of arbitrary code. See the section on [security considerations for custom code](https://docs.camunda.org/manual/7.22/user-guide/process-engine/securing-custom-code/) in the user guide for details. ## OpenAPI ````yaml POST /deployment/{id}/redeploy openapi: 3.0.2 info: title: ORION Platform REST API description: OpenApi Spec for ORION Camunda Platform REST API. version: 7.22.6-ee license: name: Apache License 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: http://{host}:{port}/{contextPath} description: The API server for the default process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest - url: http://{host}:{port}/{contextPath}/engine/{engineName} description: The API server for a named process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest engineName: default: default - url: '{url}' description: The API server with a custom url variables: url: default: '' security: - basicAuth: [] tags: - name: Authorization - name: Batch - name: Condition - name: Decision Definition - name: Decision Requirements Definition - name: Deployment - name: Engine - name: Event Subscription - name: Execution - name: External Task - name: Filter - name: Group - name: Historic Activity Instance - name: Historic Batch - name: Historic Decision Definition - name: Historic Decision Instance - name: Historic Decision Requirements Definition - name: Historic Detail - name: Historic External Task Log - name: Historic Identity Link Log - name: Historic Incident - name: Historic Job Log - name: Historic Process Definition - name: Historic Process Instance - name: Historic Task Instance - name: Historic User Operation Log - name: Historic Variable Instance - name: History Cleanup - name: Identity - name: Incident - name: Job - name: Job Definition - name: Message - name: Metrics - name: Migration - name: Modification - name: Process Definition - name: Process Instance - name: Signal - name: Schema Log - name: Task - name: Task Attachment - name: Task Comment - name: Task Identity Link - name: Task Local Variable - name: Task Variable - name: Telemetry - name: Tenant - name: User - name: Variable Instance - name: Version externalDocs: description: Find out more about ORION Rest API url: https://docs.eorion.com paths: /deployment/{id}/redeploy: post: tags: - Deployment summary: Redeploy description: >- Re-deploys an existing deployment. The deployment resources to re-deploy can be restricted by using the properties `resourceIds` or `resourceNames`. If no deployment resources to re-deploy are passed then all existing resources of the given deployment are re-deployed. **Warning**: Deployments can contain custom code in form of scripts or EL expressions to customize process behavior. This may be abused for remote execution of arbitrary code. See the section on [security considerations for custom code](https://docs.camunda.org/manual/7.22/user-guide/process-engine/securing-custom-code/) in the user guide for details. operationId: redeploy parameters: - name: id in: path schema: type: string required: true description: The id of the deployment to re-deploy. requestBody: content: application/json: schema: $ref: '#/components/schemas/RedeploymentDto' examples: example-1: summary: POST `/deployment/anDeploymentId/redeploy` value: resourceIds: - aResourceId resourceNames: - aResourceName source: cockpit responses: '200': content: application/json: schema: $ref: '#/components/schemas/DeploymentWithDefinitionsDto' examples: example-1: summary: Status 200 Response value: links: - method: GET href: >- http://localhost:38080/rest-test/deployment/aDeploymentId rel: self id: aDeploymentId name: aName source: cockpit deploymentTime: 2015-10-13T13:59:43.000+0200 tenantId: null deployedProcessDefinitions: aProcDefId: id: aProcDefId key: aKey category: aCategory description: aDescription name: aName version: 42 resource: aResourceName deploymentId: aDeploymentId diagram: aResourceName.png suspended: true tenantId: null versionTag: null deployedCaseDefinitions: null deployedDecisionDefinitions: null deployedDecisionRequirementsDefinitions: null description: Request successful. '404': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: >- Deployment or a deployment resource for the given deployment does not exist. See the [Introduction](https://docs.camunda.org/manual/7.22/reference/rest/overview/#error-handling) for the error response format. components: schemas: RedeploymentDto: title: RedeploymentDto type: object description: 'A JSON object with the following properties:' properties: resourceIds: type: array nullable: true items: type: string description: A list of deployment resource ids to re-deploy. resourceNames: type: array nullable: true items: type: string description: A list of deployment resource names to re-deploy. source: type: string nullable: true description: Sets the source of the deployment. DeploymentWithDefinitionsDto: allOf: - type: object properties: deployedProcessDefinitions: type: object nullable: true additionalProperties: $ref: '#/components/schemas/ProcessDefinitionDto' description: >- A JSON Object containing a property for each of the process definitions, which are successfully deployed with that deployment. The key is the process definition id, the value is a JSON Object corresponding to the process definition. deployedDecisionDefinitions: type: object nullable: true additionalProperties: $ref: '#/components/schemas/DecisionDefinitionDto' description: >- A JSON Object containing a property for each of the decision definitions, which are successfully deployed with that deployment. The key is the decision definition id, the value is a JSON Object corresponding to the decision definition. deployedDecisionRequirementsDefinitions: type: object nullable: true additionalProperties: $ref: '#/components/schemas/DecisionRequirementsDefinitionDto' description: >- A JSON Object containing a property for each of the decision requirements definitions, which are successfully deployed with that deployment. The key is the decision requirements definition id, the value is a JSON Object corresponding to the decision requirements definition. deployedCaseDefinitions: type: object nullable: true additionalProperties: $ref: '#/components/schemas/CaseDefinitionDto' description: >- A JSON Object containing a property for each of the case definitions, which are successfully deployed with that deployment. The key is the case definition id, the value is a JSON Object corresponding to the case definition. - $ref: '#/components/schemas/DeploymentDto' ExceptionDto: title: ExceptionDto type: object properties: type: type: string nullable: true description: An exception class indicating the occurred error. message: type: string nullable: true description: A detailed message of the error. code: type: number description: >- The code allows your client application to identify the error in an automated fashion. You can look up the meaning of all built-in codes and learn how to add custom codes in the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/error-handling/#exception-codes). ProcessDefinitionDto: type: object properties: id: type: string nullable: true description: The id of the process definition key: type: string nullable: true description: >- The key of the process definition, i.e., the id of the BPMN 2.0 XML process definition. category: type: string nullable: true description: The category of the process definition. description: type: string nullable: true description: The description of the process definition. name: type: string nullable: true description: The name of the process definition. version: type: integer format: int32 nullable: true description: >- The version of the process definition that the engine assigned to it. resource: type: string nullable: true description: The file name of the process definition. deploymentId: type: string nullable: true description: The deployment id of the process definition. diagram: type: string nullable: true description: The file name of the process definition diagram, if it exists. suspended: type: boolean nullable: true description: A flag indicating whether the definition is suspended or not. tenantId: type: string nullable: true description: The tenant id of the process definition. versionTag: type: string nullable: true description: The version tag of the process definition. historyTimeToLive: type: integer format: int32 nullable: true minimum: 0 description: >- History time to live value of the process definition. Is used within [History cleanup](https://docs.camunda.org/manual/7.22/user-guide/process-engine/history/#history-cleanup). startableInTasklist: type: boolean nullable: true description: >- A flag indicating whether the process definition is startable in Tasklist or not. DecisionDefinitionDto: type: object properties: id: type: string nullable: true description: The id of the decision definition key: type: string nullable: true description: >- The key of the decision definition, i.e., the id of the DMN 1.0 XML decision definition. category: type: string nullable: true description: The category of the decision definition. name: type: string nullable: true description: The name of the decision definition. version: type: integer format: int32 nullable: true description: >- The version of the decision definition that the engine assigned to it. resource: type: string nullable: true description: The file name of the decision definition. deploymentId: type: string nullable: true description: The deployment id of the decision definition. tenantId: type: string nullable: true description: The tenant id of the decision definition. decisionRequirementsDefinitionId: type: string nullable: true description: >- The id of the decision requirements definition this decision definition belongs to. decisionRequirementsDefinitionKey: type: string nullable: true description: >- The key of the decision requirements definition this decision definition belongs to. historyTimeToLive: type: integer format: int32 nullable: true minimum: 0 description: >- History time to live value of the decision definition. Is used within [History cleanup](https://docs.camunda.org/manual/7.22/user-guide/process-engine/history/#history-cleanup). versionTag: type: string nullable: true description: The version tag of the decision definition. DecisionRequirementsDefinitionDto: type: object properties: id: type: string nullable: true description: The id of the decision requirements definition key: type: string nullable: true description: >- The key of the decision requirements definition, i.e., the id of the DMN 1.0 XML decision definition. name: type: string nullable: true description: The name of the decision requirements definition. category: type: string nullable: true description: The category of the decision requirements definition. version: type: integer format: int32 nullable: true description: >- The version of the decision requirements definition that the engine assigned to it. resource: type: string nullable: true description: The file name of the decision requirements definition. deploymentId: type: string nullable: true description: The deployment id of the decision requirements definition. tenantId: type: string nullable: true description: The tenant id of the decisionrequirements definition. CaseDefinitionDto: type: object properties: id: type: string nullable: true description: The id of the case definition key: type: string nullable: true description: >- The key of the case definition, i.e., the id of the CMMN 2.0 XML case definition. category: type: string nullable: true description: The category of the case definition. name: type: string nullable: true description: The name of the case definition. version: type: integer format: int32 nullable: true description: The version of the case definition that the engine assigned to it. resource: type: string nullable: true description: The file name of the case definition. deploymentId: type: string nullable: true description: The deployment id of the case definition. tenantId: type: string nullable: true description: The tenant id of the case definition. historyTimeToLive: type: integer format: int32 nullable: true minimum: 0 description: >- History time to live value of the case definition. Is used within [History cleanup](https://docs.camunda.org/manual/7.22/user-guide/process-engine/history/#history-cleanup). DeploymentDto: allOf: - type: object properties: id: type: string nullable: true description: The id of the deployment. tenantId: type: string nullable: true description: The tenant id of the deployment. deploymentTime: type: string format: date-time nullable: true description: The time when the deployment was created. source: type: string nullable: true description: The source of the deployment. name: type: string nullable: true description: The name of the deployment. - $ref: '#/components/schemas/LinkableDto' LinkableDto: type: object properties: links: type: array nullable: true items: $ref: '#/components/schemas/AtomLink' description: >- The links associated to this resource, with `method`, `href` and `rel`. AtomLink: type: object properties: rel: type: string nullable: true description: The relation of the link to the object that belongs to. href: type: string nullable: true description: The url of the link. method: type: string nullable: true description: The http method. securitySchemes: basicAuth: type: http scheme: basic ````