ashb commented on issue #54778: URL: https://github.com/apache/airflow/issues/54778#issuecomment-3228287492
This wasn't possible previously in Airflow 2.x as the extra links were defined on the Operator instance, and the Webserver would create a shim/stub Operator based on the row stored in the serialized DAG, meaning any changes to these properties However with another change we made in Airflow 3.0, namely that the API server doesn't "render" the Operator links directly anymore, but instead the finalize step of the TaskSDK now calls the `get_link` method of each item in `operator_extra_links` and stores that in XCom with a defined prefix (something like `_extra_link_`) -- so we could _possibly_ do this by listing all keys that match this prefix and displaying them. Maybe. -- 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]
