ferruzzi commented on pull request #16571: URL: https://github.com/apache/airflow/pull/16571#issuecomment-879328885
Honest question: How common is it for a DAG to run for over an hour? In my limited experience, the DAGs I run generally finish way faster than that, but I'm obviously not doing enterprise-level workflows either. If we’re getting to where that is the last sticking point, would it be acceptable to get the pod operator up with that caveat and work towards extending the duration? It shouldn’t be a breaking change since the actual “get token” logic is in an internal “private” method; whatever solution we come up with for token rotation would just get implemented in that method and the user wouldn't ever know, right? Or perhaps I'm underestimating the scope of the change? To the suggestion of writing a new CLI tool to handle token rotation: I'm really not convinced that replacing the official AWS CLI tool with our own is a net gain here. There is an existing tool which is open source and maintained by the provider. What do we gain from rewriting that, other than another chunk of code to maintain and another point of failure to watch? -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
