potiuk commented on PR #28520:
URL: https://github.com/apache/airflow/pull/28520#issuecomment-1361185507
Yep. I would not like to add another "feature" for this because this can be
misused really easily. Since it can be done by POP variables, I think we should
not need to add it as a separate feature.
However I would really appreciate if you could maybe instead @kfirgollan
describe in our documentation an example workflow for development iteration
instead - including the proxy and variabkle that need to be set instead.
I think the only REALLY good use of _PIP_ADDITIONAL_REQUIREMENTS is
iteration during development and reinstalling/adding packages while restarting
your dev env. And it would be extremely valuable if someone who does it would
explain it next to the description of the variable. I think that would be
really valuable for the rest of the community.
It does not have to be very long or extensive - but showing an example
workflow where it can be used (and stressing that once you are done you should
really build your image when you deploy to production) would be super valuable
if it comes from a user like you :)
--
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]
