You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "JonnyWaffles (via GitHub)" <gi...@apache.org> on 2023/09/27 20:10:34 UTC
[GitHub] [airflow] JonnyWaffles commented on issue #31544: Possibly add a feature to "Run Tasks" from the UI
JonnyWaffles commented on issue #31544:
URL: https://github.com/apache/airflow/issues/31544#issuecomment-1738010381
Hi team, apologies for the delayed response @potiuk!
After reading through the security model, I don't really understand how force running a task is non-compliant, but then I'm no security engineer. Force running a task feels very similar in most use cases to clearing and letting the existing schedule rerun. We've always used it for administrative "break glass", where a single task may need to be executed regardless of its dependencies due to some external circumstances.
Our environment is extremely locked down, so the UI is the **only real** way to execute administrative tasks outside of a deployment pipeline. Even administrators cannot assume the Airflow identity required by CLI, because all production credentials are effectively machine read only. Only SSO, backed by multi-factor, login enables administration tasks. This feels appropriate to me because
I am definitely willing to work on this feature once it is prioritized by our internal team, but in the immediacy clearing is good enough, but I certainly miss the legacy feature.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org