Shrividya Hegde

DEV - Inspecting worker queues using keys is giving a panic error

4

The following command history indicates that on passing worker_queues.name to inspect the worker_queue name, the panic error is issued whereas for configuration and metadata sections the output seems to be...

DEV - Updating the default worker type to A5 in CeleryExecutor based deployment gives unrelated error message

2

The new deployment created has A5 as the worker type by default When the deployment is updated with the worker type as A5 with the following command as part of...

DEV - Hibernate untill timestamp doesn't reflect appropriately in the UI

5

Following command was issued to override the hibernation schedule and hibernate the deployment till the given time stamp ``` shrividyahegde@Hegde ~ % astro deployment hibernate -u 2024-02-28T21:35:46+05:30 Select a Deployment...

DEV- Workload identity string is set to empty while inspecting the deployment

4

The following is the result of inspecting a standard AWS deployment ``` shrividyahegde@Hegde ~ % astro deployment inspect Select a Deployment # DEPLOYMENT NAME RELEASE NAME DEPLOYMENT ID DAG DEPLOY...

DEV- Min worker count default help command text needs to be changed

2

The default value for the min worker count for a Celery deployment is 0 in the UI and in the CLI but the help command issued for default worker queue...

DEV-The default workflow for deployment creation while deploying dags is "Dedicated" instead of "Standard"

2

As a user I tried deploying a dag into a workspace that has no deployments in it. The CLI prompted for deployment creation but later the cluster name was offered...

User is able to create a deployment under an already created cluster (dedicated /shared).However, there is no provision at the moment to create a dedicated cluster under the given organization...