Deployment

This guide demonstrates how to set up and configure Deployments in Ascend with proper separation between Development, Staging, and Production Environments.

The same process outlined here can be repeated to create Staging and Production environments, aligning with software engineering best practices for a complete CI/CD workflow.

To learn more about Deployments, check out this concept guide.

Prerequisites

• Ascend Project
• Ascend Workspace
• Ascend Flow with at least one Connection
• Dedicated Profiles for Development, Staging, and Production Deployments
• Configured Environments for Development, Staging, and Production as described in the Quickstart guides

Creating a Development Deployment

1. Navigate to the Projects and Deployments section in your Settings.

2. Locate your desired Project and select Add Deployment.

3. Configure your Deployment with the following settings:

   • Title: Enter Development or another descriptive name
   • Environment: Select your Development environment
   • Branch: Specify your Development branch (typically main, which is also the base branch)
   • Profile: Choose your dedicated development Deployment profile
   • Size: Select appropriate compute resources based on your workload requirements

   

4. Click Save to create the Deployment.

5. Access your newly created Deployment either through the home page or by returning to the Projects and Deployments section in Settings.

Managing your Deployment

Once your Development Deployment is active, you can:

• Run your Flows within this isolated environment
• Make changes and test them without affecting production
• Monitor performance and resource usage
• Debug issues specific to this environment

Deployment promotion pipeline

Follow the same steps as above to create Staging and Production Deployments, adjusting the configuration appropriately:

• Staging: Connect to your staging environment and use a dedicated staging branch
• Production: Connect to your production environment and use a dedicated production branch

To effectively manage the promotion of changes across Development, Staging, and Production deployments, implement GitOps best practices:

1. Develop and test changes in your Development environment
2. When ready, merge your feature branch into the staging branch to deploy to Staging
3. After thorough testing in Staging, merge the staging branch into the production branch to deploy to Production

This structured promotion process ensures that each change is validated before reaching Production, minimizing risks and maintaining the stability of your data pipelines.

🎉 Congratulations! You've successfully set up your Deployment infrastructure in Ascend, enabling a robust development workflow.