RafiB982 commented on issue #59846: URL: https://github.com/apache/airflow/issues/59846#issuecomment-3693945224
Hi @potiuk I've reviewed the Airflow CLI commands for managing connections, and it seems that airflow connections list and airflow connections get serve distinct and complementary purposes: airflow connections list (with options like --output json or filtering) provides an overview of all available connections (or filtered subsets), showing basic info like conn_id and conn_type. This is useful for discovery, auditing, or scripting when you need to see what connections exist. airflow connections get <conn_id> retrieves the full details (including host, login, extra fields, etc.) of a single specific connection. I'm curious to better understand your view: in what scenario or use case do you see airflow connections list as redundant to airflow connections get? For example, is there a way to achieve the same listing/overview functionality purely with get, or a specific workflow where list isn't needed? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
