potiuk commented on pull request #11157: URL: https://github.com/apache/airflow/pull/11157#issuecomment-699939675
> The "not advertising it outside of dev list" answers my question, yes > We should make RBAC the default (change `--use-rbac` in to `--no-rbac`) Feel free :) . It's a v1-10-test only feature and can be changed any time :) > That said, a lot of what breeze does is around mouting files, taking care of rebuilds, cachine, and the like - none of which is strictly necessary or needed when running and installing releases from PyPi. For users wanting to run Airflow a much simpler solution is a single Docker compose file -- all we have to worry about mounting for them is AIRFLOW_HOME folder. Something like https://github.com/puckel/docker-airflow/blob/master/docker-compose-LocalExecutor.yml Absolutely - there is an Umbrella issue for that: #8548 which links to some good examples that users contributed and it would be great if that one gets implemented. There are few people who volunteered for it at different times. This docker-compose should be both development and production-friendly. However, I believe it is more important for production deployments especially if the compose specification https://www.docker.com/blog/announcing-the-compose-specification/ will get a "released" stage. It's based on docker-compose to start with, but it will become an open standard (docker-compose is not). For development environments, I think it is much more important to have devcontainer.json integration https://code.visualstudio.com/docs/remote/devcontainerjson-reference that will allow running the full development environment in GitHub once CodeSpaces go out of beta (in Q4 so quite soon). I looked at it when developing breeze and I made sure it will be very easy to integrate those two. Then for those who would not like CodeSpaces, they will continue having "agnostic" Breeze and for those who would like point-and-run in web, Codespaces will also work using the same "engine" under the hood (it's mostly about automatically building and updating the right docker image and starting integrations if needed). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
