📄️ Schedule a Deployment
Using Deploy, you can schedule deployment tasks for execution at a specified moment in time. For more information, see scheduling tasks.
📄️ Set up Concurrent Deployments
In Deploy with the custom microservices deployment technologies, concurrent deployments are causing issues because of middleware limitations that allow only for a single deployment to be performed to the target at a given time.
📄️ Preview the Deployment Plan
When you set up an initial deployment or an update, you can use the Preview option to view the deployment plan that Deploy generated based on the deployment configuration. As you map deployables to containers in the deployment configuration, the Preview will update and show changes to the plan.
📄️ Deploy an Application
To complete this tutorial, you must have your Deploy infrastructure and environment defined, and have added or imported an application to Deploy. For more information, see Connect Deploy to your infrastructure, Create an environment in Deploy, and Import a package instructions.
📄️ View Deployment History
You can view the history of successful deployments of application versions to an environment. This is useful when you want to determine placeholder value changes between versions for an environment, determine who made a specific change, and to support deployment rollbacks.
📄️ Update a Deployed Application
In Deploy, you do not need to manually create a delta package to perform an update, the Deploy auto-flow engine calculates the delta between two packages automatically. For more information, see what's in an application deployment package.
📄️ Use the Deployment Pipeline
In Deploy you can view the deployment pipeline for an application or a deployment/provisioning package. In the deployment pipeline you can view the sequence of environments to which an application is deployed during its lifecycle. The deployment pipeline also allows you to see the data about the last deployment of an application to each environment. You must first define a deployment pipeline for each application you want to view.
📄️ Use Tags to Configure Deployments
In Deploy, you can use the tagging feature to configure deployments by marking which deployables should be mapped to which containers. By using tagging, in combination with placeholders, you can prepare your deployment packages and environments to automatically map deployables to containers and configuration details at deployment time.
📄️ Create a Dictionary
Placeholders are configurable entries in your application that will be set to an actual value at deployment time. This makes the deployment package environment-independent and reusable. At deployment time, you can provide values for placeholders manually or they can be resolved from dictionaries that are assigned to the target environment.
📄️ Use JSON Patch Editor
JSON Patch is a format for describing changes to a JSON document. It can be used to avoid sending a whole document when only a part has changed.
📄️ Use Patch Dictionaries
This topic provides an overview of the patch dictionary feature and an example scenario that shows how you can use patch dictionaries to manage the substitution of configuration values during application deployment.
📄️ Stop, Abort, or Cancel a Deployment
Stop a running deployment
📄️ Perform Hot Deployments
This topic describes how to perform "hot" deployments with Deploy. Hot deployment is the practice of updating an application without restarting infrastructure or middleware components.
📄️ Perform Dark Launch Deployments
This topic describes how to perform "dark launch" deployments using Deploy. Dark launch is a go-live strategy in which code implementing new features is released to a subset of the production environment but is not visibly activated or is only partially activated. With this strategy, the code can be tested in a production setting without users being aware of it.
📄️ Perform Canary Deployments
This topic describes how to perform "canary" deployments using Deploy. Canary deployment is a pattern in which applications or features are released to a subset of users before being rolled out across the entire user base. This is typically done to reduce the risk when releasing new features, so any issues impact a smaller portion of the overall user base.