Migrate existing objects to the Environment Manager

You can bring existing Airflow connections, Airflow variables, environment variables, and metrics exports into the Astro Environment Manager. After an object is in the Environment Manager, you can manage it centrally in the Workspace and link it to other Deployments or to Astro IDE projects.

This page covers two flows:

• Migrate from Airflow. Bulk migrate connections and Airflow variables from a Deployment’s Airflow metadata database into the Environment Manager.
• Promote to Workspace Environment. Promote a single Deployment-scoped connection, Airflow variable, environment variable, or metrics export to the Workspace level.

Each flow keeps the source object available on the Deployment by linking the new Workspace environment object back to that Deployment.

Migrate Airflow connections and variables from a Deployment

The Migrate from Airflow flow reads connections and Airflow variables from a Deployment’s Airflow metadata database, copies each one into a Workspace environment object linked to the source Deployment, and removes it from the metadata database.

Prerequisites

• Workspace Owner user permissions.
• A standard Astro Deployment with one or more connections or Airflow variables stored in its metadata database. Remote Execution Deployments aren’t supported.

Migrate a connection or Airflow variable

The migration page provides separate entry points for connections and Airflow variables. The steps are equivalent for both object types.

1. In the Astro UI, select the Deployment that contains the objects you want to migrate, then click the Environment tab.
2. Click Connections or Airflow Variables in the Deployment Environment menu.
3. Click Migrate from Airflow. The action appears dimmed when the Deployment’s metadata database doesn’t contain any objects of that type.
4. In the migration page, select the connections or Airflow variables you want to migrate. Each row shows whether the object is new to the Workspace or whether a Workspace object with the same key already exists. If a matching Workspace object already exists, Astro creates a Deployment-level override on that Workspace object rather than a duplicate.
5. Click Migrate, then confirm in the dialog. The confirmation warns that Astro removes the source objects from the Deployment’s metadata database.

After the migration completes, the new objects appear in the Workspace Environment page. Each migrated object is linked to the source Deployment, so the Deployment continues to use the same values. The objects aren’t automatically available to other Deployments or Astro IDE projects. To use a migrated object elsewhere, link it from the Workspace Environment page. See Link connections to Deployments or Link connections to Astro IDE projects.

Promote a Deployment environment object to the Workspace

You can promote a Deployment-scoped connection, Airflow variable, environment variable, or metrics export to the Workspace level. After promotion, the object is managed in the Workspace and remains linked to the source Deployment, so the Deployment continues to use the same values.

Prerequisites

• workspace.envObjects.create and deployment.update permissions, included with Workspace Operator or Workspace Owner user permissions.
• A Deployment-scoped object that isn’t already an override of a Workspace-level object.

Promote an object

1. In the Astro UI, select the Deployment that contains the object.
2. Click the Environment tab in the Deployment menu, then open Connections, Airflow Variables, Environment Variables, or Metrics Exports.
3. Open the row-level more actions menu for the object you want to promote.
4. Select Promote to Workspace Environment.
5. Confirm the promotion in the dialog. For environment variables, enter the environment variable key to confirm.

After promotion, the object appears in the Workspace Environment page. You can link it to additional Deployments and Astro IDE projects from there.

If a Workspace object with the same type and key already exists, Astro adds a Deployment-level override on the existing Workspace object instead of creating a duplicate.

See also

• Manage Airflow connections, variables, and environment variables
• Create connections in Astro
• Create Airflow variables in Astro
• Create environment variables in Astro