--remote-execution-enabled flag creates standard deployment instead of failing or prompting for required config #1895
Description
Describe the bug
When using the --remote-execution-enabled flag with astro deployment create, the CLI proceeds to create a Standard deployment (either with Celery or Astro executor), even though the intention was to create a Remote Execution deployment.
This can lead to unexpected deployment types being created without any warning or guidance.
deeksha@Deekshasahus-MacBook-Pro ~ % /usr/local/bin/astro deployment create -n "test_cli_remote_execution" --remote-execution-enabled
Current Workspace: qa_test
Please select a Region for your Deployment:
# REGION
1 westeurope
2 westus2
3 eastus2
4 australiaeast
> 2
NAME NAMESPACE CLUSTER CLOUD PROVIDER REGION DEPLOYMENT ID RUNTIME VERSION DAG DEPLOY ENABLED CI-CD ENFORCEMENT DEPLOYMENT TYPE
test_cli_remote_execution astral-function-6099 N/A AZURE westus2 cmd8i5vyj032801nz220ag8cu 3.0-5 (based on Airflow 3.0.3) false false STANDARD
Successfully created Deployment: test_cli_remote_execution
Deployment can be accessed at the following URLs
Deployment Dashboard: cloud.astronomer-dev.io/cm6kqel7k00pv01o9ftlsxvha/deployments/cmd8i5vyj032801nz220ag8cu
Airflow Dashboard: clztuyh0a01z701mwxjahsza2.astronomer-dev.run/d20ag8cu?orgId=org_bql5Hn1KELMRNPoM
deeksha@Deekshasahus-MacBook-Pro ~ % /usr/local/bin/astro deployment create -n "test_cli_remote_execution" --remote-execution-enabled --executor Astro
Current Workspace: qa_test
Please select a Region for your Deployment:
# REGION
1 westeurope
2 australiaeast
3 westus2
4 eastus2
> 3
Error: Invalid request: Deployment name 'test_cli_remote_execution' already exists in this workspace
deeksha@Deekshasahus-MacBook-Pro ~ % /usr/local/bin/astro deployment create -n "test_cli_remote_execution_create" --remote-execution-enabled --executor Astro
Current Workspace: qa_test
Please select a Region for your Deployment:
# REGION
1 eastus2
2 westeurope
3 westus2
4 australiaeast
> 3
NAME NAMESPACE CLUSTER CLOUD PROVIDER REGION DEPLOYMENT ID RUNTIME VERSION DAG DEPLOY ENABLED CI-CD ENFORCEMENT DEPLOYMENT TYPE
test_cli_remote_execution_create energetic-frequency-8366 N/A AZURE westus2 cmd8n2scr04t801qdn9xeqkul 3.0-5 (based on Airflow 3.0.3) false false STANDARD
Successfully created Deployment: test_cli_remote_execution_create
Deployment can be accessed at the following URLs
Deployment Dashboard: cloud.astronomer-dev.io/cm6kqel7k00pv01o9ftlsxvha/deployments/cmd8n2scr04t801qdn9xeqkul
Airflow Dashboard: clztuyh0a01z701mwxjahsza2.astronomer-dev.run/d9xeqkul?orgId=org_bql5Hn1KELMRNPoM```
**What CLI Version did you experience this bug?**
1.35.1
Metadata
Metadata
Assignees
Labels
No labels