Skip to main content

Previewing and finalizing your deployment

Support avatar
Written by Support
Updated over 4 months ago

In every deployment, the step just before deploying your changes is the Deployment Preview. This step helps you:

  1. Review the changes to be deployed

  2. Review errors preventing changes from being deployed

  3. Review additional warnings and informational messages

  4. Make additional edits to your deployed elements

Review the changes to be deployed

After selecting the changes to be deployed in the previous step, Tulip calculates the "deploy plan" for your deployment - which API calls to make, in what order, and which elements can or can’t be deployed because of various constraints and generates and overview of your deployment.

Switching to 'Elements' view from the top right corner, you can review the elements you selected for deployment. Each element will be marked as Will deploy = Yes or No.

You can also focus only on additions, removals or modifications, by using the table-tabs above the table.

If you realize there are additional changes that you forgot to include in this deployment, you can always go back to the element selection phase. Note that edits that you’ve made will be discarded in this case.

Reviewing errors and warnings

Elements which are marked as 'Will deploy = No' have some issues that prevent them from being deployed - Tulip will not attempt to deploy them.

Click an element which has issues to review the issues preventing their deployment.

In addition, some elements that are planned to be deployed may also have some warnings or informational messages, which do not prevent them from being deployed. Click the elements to learn more about these more.

Editing Elements

If your deployment requires some additional changes to the deployed elements, which were not part of the elements in the source application connection, you can use the “Edit” button to edit the element itself. This edit will be applied only to the target application connection element, once the deployment is made. You can also edit additional target elements as part of the deployment, by selecting them from the “All” tab and editing them.

Read more about these options in the "Editing files during deployments" article.

Deploying your changes

When you’re done reviewing the plan, proceed to deploying them by clicking “Deploy” on the bottom right corner of the screen. This process may take some time; you can review its progress in the top progress bar.

📘 When clicking deploy, you may see a popup with a list of pre-deploy actions you need to perform on the service side. For example, when deploying configuration changes to a security application, you may need to disable certain policies before deploying. Follow the on-screen instructions, and if necessary the links for additional documentation about each recommended action

Deployment summary

Once the deployment is complete, Tulip presents the deployment summary - which elements were successfully deployed, which weren’t, and additional errors to review.
Review the “Deployed” and “Failed to Deploy” table-tabs to see the deploy results.
You can also review any deployment errors in the “Deploy Errors” tab.

📘 When deploy ends, you may see a popup with a list of post-deploy actions you need to perform on the service side. For example, when deploying configuration changes to a security application, you may need to re-enable certain policies after deploying. Follow the on-screen instructions, and if necessary the links for additional documentation about each recommended action. You can click “Recommended Actions”, when available, to see these actions.

Did this answer your question?