GitHub user bennage added a comment to the discussion: override simple auth manager for `airflow standalone` to use provided config
I don't have a strong opinion about what `standalone` ought to be. Maybe there's a better way to do what we're trying to do. Here's more context. We have a custom plugin that extends the native API. I don't think the functionality of the plugin is important, but happy to share if you think it matters. We're using a devcontainer that includes Airflow. Our devs are frequently spinning up Airflow from the devcontainer to test functionality in the plugin or to test a dag. As a _convenience_, we have been doing that with `standalone`. What's the recommended approach? GitHub link: https://github.com/apache/airflow/discussions/53225#discussioncomment-13746338 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
