What options have people discovered to stand in the place of ExternalTaskSensor and ExternalTaskMarker across deployments? I know normally with coupling we’d try to keep things on the same deployment. But in this case Deployment A is meant to be rock solid and Deployment B is meant to be experimental/wild west. Any ideas?
I ended up treating Deployment A’s metadata database as just another SQL Server and poked it with an SQLSensor. Probably not ideal, but it worked on the sensor side. Nothing for a Marker. Would probably have to leverage the Airflow 2.x API.