Home Original page

Add "REMOTE EXECUTION" column to deployment tables by ronidelacruz-astro · Pull Request #1952 · astronomer/astro-cli

Skip to content

Navigation Menu

Sign in

Appearance settings

Conversation

@ronidelacruz-astro

Description

Add remote execution status col to deployment display table

🎟 Issue(s)

Related #1897

🧪 Functional Testing

./astro deployment create -n "test_cli_remote_execution_create_3"  --remote-execution-enabled --executor Astro --type dedicated 

Current Workspace: roni


Please select a Cluster for your Deployment:
 #     CLUSTER NAME             CLOUD PROVIDER     CLUSTER ID                    
 1     Astro Agent CI_DND       AZURE              cmbjc2euc03ak01nlfpy5xtwr     
 2     airflow3-testing_DND     AZURE              cm4sauxuo03ig01rfux2aun5d     

> 2
 NAME                                   NAMESPACE                 CLUSTER                  CLOUD PROVIDER     REGION      DEPLOYMENT ID                 RUNTIME VERSION                    DAG DEPLOY ENABLED     CI-CD ENFORCEMENT     DEPLOYMENT TYPE     REMOTE EXECUTION     
 test_cli_remote_execution_create_3     uniform-buoyancy-7912     airflow3-testing_DND     AZURE              westus2     cmgguhtpl011501owe9woezt9     3.1-1 (based on Airflow 3.1.0)     false                  false                 DEDICATED           true                 

 Successfully created Deployment: test_cli_remote_execution_create_3
 Deployment can be accessed at the following URLs 

 Deployment Dashboard: cloud.astronomer-dev.io/cmfvjgjhv00hg01qj5115yydj/deployments/cmgguhtpl011501owe9woezt9
 Airflow Dashboard: clztuyh0a01z701mwxjahsza2.astronomer-dev.run/d9woezt9

📸 Screenshots

Add screenshots to illustrate the validity of these changes.

📋 Checklist

  • Rebased from the main (or release if patching) branch (before testing)
  • Ran make test before taking out of draft
  • Ran make lint before taking out of draft
  • Added/updated applicable tests
  • Tested against Astro-API (if necessary).
  • Tested against Houston-API and Astronomer (if necessary).
  • Communicated to/tagged owners of respective clients potentially impacted by these changes.
  • Updated any related documentation

feluelle

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any existing UTs for this we should update?

@ronidelacruz-astro

No, we check for success, nothing to check for outputs

2 participants

@ronidelacruz-astro @feluelle