jason810496 opened a new pull request, #54651: URL: https://github.com/apache/airflow/pull/54651
related: #52712 related discussion: https://github.com/apache/airflow/pull/53556#discussion_r2265242503 ## Why Here are some advantages of using "scheme+passing keyword parameters directly from MessageQueueTrigger" instead of the "Queue URI" interface: 1. It is more secure than explicitly including the host, port, and URI at the Dag code level. 2. It is less confusing for users, as specifying the "host" and "port" in the URI could conflict with the current Airflow Connection feature and create ambiguity. For more details, please refer to the discussion at: https://github.com/apache/airflow/pull/53556#discussion_r2265242503 ## What - The `queue` URI parameter should be replaced by the `scheme` parameter for matching the provider's queue. - The remaining parameters required by the provider's trigger (e.g., `AwaitMessageTrigger`, `SqsSensorTrigger`) should be passed directly from `MessageQueueTrigger`. - Provide a backward-compatible interface for using the `queue` URI. - This is mainly for AWS SQS and Apache Kafka. - Since Redis Queue has not been released yet, we can simply replace the "queue" logic with the "scheme" logic. - Add a deprecation warning for the `queue` parameter in both logging and documentation. -- 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]
