Re: [VOTE] September 2022 PR of the Month

2022-09-27 Thread Beck, Vincent
Same here. Less code, more happiness 😊 https://github.com/apache/airflow/pull/23592 From: Bas Harenslak Reply-To: "dev@airflow.apache.org" Date: Tuesday, September 27, 2022 at 2:13 PM To: "dev@airflow.apache.org" Subject: RE: [EXTERNAL][VOTE] September 2022 PR of the Month CAUTION: This ema

Re: [ANNOUNCE] New committer Andrey Anshin (Taragolis)

2022-12-02 Thread Beck, Vincent
Congrats! Well deserved! ï»żOn 2022-12-02, 2:31 AM, "Jarek Potiuk" wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hello Airflow Community, I am happy to

Re: [DISCUSS] AIP-52 Automatic setup and tear down tasks

2022-12-20 Thread Beck, Vincent
Same here! I’d love to see these in my DAGs 😊 From: Pierre Jeambrun Reply-To: "dev@airflow.apache.org" Date: Tuesday, December 20, 2022 at 7:52 AM To: "dev@airflow.apache.org" Subject: RE: [EXTERNAL][DISCUSS] AIP-52 Automatic setup and tear down tasks CAUTION: This email originated from outsi

Re: [ANNOUNCE] New committer Niko Oliveira (o-nikolas)

2022-12-20 Thread Beck, Vincent
Congrats Niko!! 😊 From: Pankaj Singh Reply-To: "dev@airflow.apache.org" Date: Monday, December 19, 2022 at 9:13 PM To: "dev@airflow.apache.org" Subject: RE: [EXTERNAL][ANNOUNCE] New committer Niko Oliveira (o-nikolas) CAUTION: This email originated from outside of the organization. Do not cli

Re: [VOTE] AIP-52 Automatic setup and teardown tasks

2023-01-09 Thread Beck, Vincent
Would love to see this one going through ! +1 (non binding) From: Ash Berlin-Taylor Reply-To: "dev@airflow.apache.org" Date: Monday, January 9, 2023 at 11:27 AM To: "dev@airflow.apache.org" Subject: [EXTERNAL] [VOTE] AIP-52 Automatic setup and teardown tasks CAUTION: This email originated fr

Amazon provider package system tests dashboard

2023-01-23 Thread Beck, Vincent
The AWS Airflow team is happy to announce that the dashboard we have been building which summarizes the health status of system tests within the Amazon provider package is now available here: https://aws-mwaa.github.io/open-source/system-tests/dashboard.html. The purpose is to share with anyone

Re: Seeking Feedback for Airflow Multi-Tenant Model Proposal

2023-02-02 Thread Beck, Vincent
56w8UKgQS1-CbGPu2OFr4l9lDaUnXbN8/edit?usp=sharing. If you agree with this proposal, would it be possible to have permissions to create an AIP? Thank you, Vincent From: "Mehta, Shubham" Date: Tuesday, January 10, 2023 at 3:01 AM To: "dev@airflow.apache.org" Cc: "Beck, V

Re: Seeking Feedback for Airflow Multi-Tenant Model Proposal

2023-02-03 Thread Beck, Vincent
Thank you! https://cwiki.apache.org/confluence/display/~vin100.beck ï»żOn 2023-02-02, 5:38 PM, "Jarek Potiuk" wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.

Re: Seeking Feedback for Airflow Multi-Tenant Model Proposal

2023-02-03 Thread Beck, Vincent
Thanks __ ï»żOn 2023-02-03, 10:55 AM, "Jarek Potiuk" wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Added. On Fri, Feb 3, 2023 at 3:53 PM Bec

Re: Seeking Feedback for Airflow Multi-Tenant Model Proposal

2023-02-13 Thread Beck, Vincent
nsider the concept of a "user management provider" with a simple built-in implementation being the current Airflow functionality, enabling alternate more complex (but separate) implementations such as your proposal here as alternate user management providers. Maybe, this also enables us

Re: [LAZY CONSENSUS] Unsubscribe links in users@ mailing list footers

2023-03-03 Thread Beck, Vincent
+1 From: Elad Kalif Reply-To: "dev@airflow.apache.org" Date: Friday, March 3, 2023 at 9:50 AM To: "dev@airflow.apache.org" Subject: RE: [EXTERNAL][LAZY CONSENSUS] Unsubscribe links in users@ mailing list footers CAUTION: This email originated from outside of the organization. Do not click l

Re: Seeking Feedback for Airflow Multi-Tenant Model Proposal

2023-03-08 Thread Beck, Vincent
arating the FAB provider and designing the Airflow Authorization API. We will share our findings with the community as a GitHub discussion and may even do a PoC if necessary. @Community, if you are an expert in authorization or FAB and interested in collaborating on this effort, please contact me o

AIP-56 Extensible user management

2023-03-28 Thread Beck, Vincent
Hi all, I would like to get your feedback on an AIP I wrote: "Extensible user management". This AIP is a follow-up on a discussion we had in this email list on the multi tenancy topic. I decided to create a new email thread because I feel the topic had diverged a bit from the original topic (mu

Re: [DISCUSS] Exclude some providers that hold us back from releasing

2023-03-29 Thread Beck, Vincent
+1 ï»żOn 2023-03-29, 2:26 AM, "Elad Kalif" mailto:elad...@apache.org>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. I agree that we should exclude providers tha

Re: [DISCUSS] Describing (new) provider approval policies

2023-03-30 Thread Beck, Vincent
Big yes to "WDYT about documenting those policies in this way?". That would finally set the rules and process to add a new provider. It will make it clearer for anyone who's thinking of creating a new provider and potentially avoid question we already had in the past in this email list (even tho

Re: [ANNOUNCE] New committer Hussein Awala

2023-04-11 Thread Beck, Vincent
Congrats! __ ï»żOn 2023-04-11, 3:54 PM, "Pierre Jeambrun" mailto:pierrejb...@gmail.com>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Congratulations Hussein, w

Re: AIP-56 Extensible user management

2023-05-02 Thread Beck, Vincent
> I promise to provide my feedback by the end of the week, sorry for > > delaying it, but we had some 2.6 preparation, branching, feature flags > etc. > > also for AIP-44 and I am getting back on track with that one soon. > > > > On Fri, Mar 31, 2023 at 9:35 AM Mehta, Sh

Re: AIP-56 Extensible user management

2023-05-09 Thread Beck, Vincent
ated Rest APIs and CLI commands from Airflow. That will indeed make the >> AIP way simpler and shorter >> >> I don't think we can do that: we still need to consider users when they >> are just getting started out with Airflow -- if we only cater to giant >> enterpris

Re: AIP-56 Extensible user management

2023-05-16 Thread Beck, Vincent
ial? We have this possibility in standard “plugins”. I suggest using that framework * What is the need for “get_user_name”? Are we going to invent our own Framework? Otherwise Flask might work? Cheers Bolke On 9 May 2023 at 19:55:32, Beck, Vincent (vincb...@amazon.com.inva <mailto:vinc

Re: [VOTE] Airflow Providers prepared on May 16, 2023

2023-05-17 Thread Beck, Vincent
+1 (non-binding). I tested amazon provider packages with some testing DAGs. ï»żOn 2023-05-17, 1:39 PM, "Jarek Potiuk" mailto:ja...@potiuk.com>> wrote: +1 (binding) - checked all my changes, checked signatures, checksums, licences for all providers. All looks good. On Wed, May 17, 2023 at 3:25 PM

Re: AIP-56 Extensible user management

2023-05-24 Thread Beck, Vincent
> > > > > > > > Please have a look at flask login ( > > https://flask-login.readthedocs.io/en/latest/ > > <https://flask-login.readthedocs.io/en/latest/>) or even base your design > > upon Flask-Login. This ensures that the right information is availab

Re: AIP-56 Extensible user management

2023-05-30 Thread Beck, Vincent
your design > > upon Flask-Login. This ensures that the right information is available > > across all components in a way that Flask components understand. The > > question then becomes how does the DAG subsystem (which does not rely on > > Flask) deal with this. It might need a kind

Re: AIP-56 Extensible user management

2023-06-05 Thread Beck, Vincent
th manager can retrieve them itself when processing the "is_authorized" request. Any context information related to resources are welcome to be added in the context of the "is_authorized" API, but I don’t think we should add context information related to users. Vincent ï»żOn 202

Re: Deferrable operators in system tests, how?

2023-06-07 Thread Beck, Vincent
Same here, I like the breeze option ï»żOn 2023-06-07, 3:32 AM, "Pankaj Koti" mailto:pankaj.k...@astronomer.io.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.

Re: [ANNOUNCE] New committer: Pankaj Singh

2023-06-12 Thread Beck, Vincent
Congrats! ï»żOn 2023-06-12, 5:28 PM, "Kaxil Naik" mailto:kaxiln...@apache.org>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Hello Airflow Community, I am hap

Re: [VOTE] Release Airflow 2.6.2 from 2.6.2rc1

2023-06-13 Thread Beck, Vincent
+1 (non-binding) Tested against my testing DAGs. ï»żOn 2023-06-13, 12:04 PM, "Pankaj Koti" mailto:pankaj.k...@astronomer.io.inva>LID> wrote: +1 (non-binding) Tested my set of changes and additionally ran a few DAGs. Regards, Pankaj Koti *Senior Software Engineer, *OSS Engineering Te

Re: [VOTE] Release Airflow 2.6.2 from 2.6.2rc2

2023-06-15 Thread Beck, Vincent
+1 (non binding) Tested against my testing DAGs. I also run all AWS system tests against 2.6.2rc2 and most of them pass. After investigation, the few failures are not related to Airflow new version. You can see the result here: https://aws-mwaa.github.io/open-source/system-tests/version/2.6.2rc

Re: AIP-56 Extensible user management

2023-06-16 Thread Beck, Vincent
Thanks for the feedback Jed, that's something I confess I had not thought about. It is a valid concern. What I can propose as a compromise is to leave the "move FAB auth manager to a separate provider" task to the end of the project and mark it as optional. In other words, we can build everythin

[VOTE] AIP-56 Extensible user management

2023-06-19 Thread Beck, Vincent
Dear Airflow community, I would like to start a vote for "AIP-56 Extensible user management". You can find the AIP here: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-56+Extensible+user+management Discussion thread: https://lists.apache.org/thread/ck8dsj5w82lvr0cpwr4wlptmydqwnsqc Th

Re: AIP-56 Extensible user management

2023-06-20 Thread Beck, Vincent
: +91 9730079985 On Fri, Jun 16, 2023 at 10:21 PM Jed Cunningham mailto:jedcunning...@apache.org>> wrote: > Sounds good to me. Hopefully we can make it happen, but we give ourselves > an escape hatch :) > > On Fri, Jun 16, 2023 at 9:45 AM Beck, Vincent <mailto:vincb.

Re: [VOTE] Airflow Providers prepared on June 20, 2023

2023-06-21 Thread Beck, Vincent
+1 (non-binding) I tested my set of changes in apache-airflow-providers-cncf-kubernetes==7.1.0rc1 and it works as expected. I also ran my testing DAGs with no issue. I also ran AWS system tests against apache-airflow-providers-amazon==8.2.0rc1 and they all succeed. You can see the dashboard here

[RESULT][VOTE] AIP-56 Extensible user management

2023-06-26 Thread Beck, Vincent
Hello, AIP-56 has been accepted. 3 +1 binding votes received: - Jarek Potiuk - Niko Oliveira - Hussein Awala 6 +1 non-binding votes received: - Shubham Mehta - Dennis Ferruzzi - Phani Kumar - Pankaj Koti - Raphael Vandon - Vincent Beck I will create issues to track the different tasks related t

Re: AIP-56 Extensible user management

2023-06-28 Thread Beck, Vincent
it to you. If you also think some tasks are missing, feel free to create them directly. ï»żOn 2023-06-20, 10:54 AM, "Beck, Vincent" mailto:vincb...@amazon.com.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments

Re: [VOTE] June 2023 PR of the Month

2023-06-29 Thread Beck, Vincent
My vote goes for #31123 as well! Nice one. ï»żOn 2023-06-29, 10:59 AM, "Kaxil Naik" mailto:kaxiln...@gmail.com>> wrote: +1 for #31123 👏 On Thu, 29 Jun 2023 at 14:33, Pankaj Koti mailto:pankaj.k...@astronomer.io.inva>lid> wrote: > Yes, +1 also from me for #31123. > Thank you for the poll! > >

Re: [DISCUSS] Moving Dask Executor to a separate (optional?) dask provider

2023-07-20 Thread Beck, Vincent
My opinion is I would rather not preinstall Dask provider because as already mentioned in this thread, this is not technically a breaking change. Users using Dask provider will be able to find out quite easily that their environment is not working without Dask dependency. To me it makes more sen

Re: [VOTE] Make (soon coming) dask provider preinstalled

2023-07-21 Thread Beck, Vincent
-1 (non-binding) ï»żOn 2023-07-21, 5:46 AM, "MichaƂ Modras" mailto:michalmod...@google.com.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. -1 (non-bindin

Re: [ANNOUNCE] New PMC member: Hussein Awala

2023-07-31 Thread Beck, Vincent
Congratulations Hussein! ï»żOn 2023-07-30, 5:41 AM, "utkarsh sharma" mailto:utkarshar...@gmail.com>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Congratulation

Re: [VOTE] The daskexecutor, cncf.provider, celery providers in 2.7.0. as regular not-preinstalled providers

2023-07-31 Thread Beck, Vincent
I vote for a ï»żOn 2023-07-30, 12:24 AM, "Amogh Desai" mailto:amoghdesai@gmail.com>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. I also think that these o

Re: [VOTE] Airflow Providers prepared on July 29, 2023

2023-07-31 Thread Beck, Vincent
+1 (non-binding). I tested the Amazon provider package against my testing DAGs. ï»żOn 2023-07-31, 11:03 AM, "Pankaj Singh" mailto:ags.pankaj1...@gmail.com>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the se

[DISCUSS] Move FAB auth manager to a new provider

2023-11-14 Thread Beck, Vincent
Hello, I am sending this email to gather feedbacks/concerns on what is going to happen regarding AIP-56 (https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-56+Extensible+user+management). The majority of the work related to AIP-56 is now completed. As a summary, all the code related to us

[LAZY CONSENSUS] Add fab provider

2023-11-21 Thread Beck, Vincent
Hello everyone, Following the discussion about moving the FAB auth manager to a new provider, I am calling for a lazy consensus on creating a new provider to the Airflow repo which would include this FAB auth manager. Discussion thread: https://lists.apache.org/thread/70gyol2jwn6b39owgyg53c4k6

[DISCUSS] External event driven scheduling in Airflow

2024-07-25 Thread Beck, Vincent
Hello everyone, I created a draft AIP regarding "External event driven scheduling in Airflow". This proposal is about adding capability in Airflow to schedule DAGs based on external events. Here are some examples of such external events: - A user signs up to one of the user pool defined in my cl

[VOTE] AIP-82 - External event driven scheduling in Airflow

2024-08-02 Thread Beck, Vincent
Hi everyone, I would like to call for a vote on AIP-82 External event driven scheduling in Airflow. AIP link: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-82+External+event+driven+scheduling+in+Airflow Discussion thread: https://lists.apache.org/thread/b7kl9sng7zn81dchn5nqom336ql5p

[RESULT][VOTE] AIP-82 External event driven scheduling in Airflow

2024-08-12 Thread Beck, Vincent
Hi everyone, The vote for AIP-82 has passed. AIP-82 External event driven scheduling in Airflow https://cwiki.apache.org/confluence/x/egzOEg Discussion thread https://lists.apache.org/thread/b7kl9sng7zn81dchn5nqom336ql5pnf2 Vote thread: https://lists.apache.org/thread/k0386wy6tlvsz6vlhn88k58kzt

Re: [DISCUSS] - Policy for removing deprecated code from providers

2022-05-20 Thread Beck, Vincent
Hello, Very good topic to discuss! I would like to clarify something before diving in the topic, when you say “the provider's releases are very frequent (almost monthly)”, are you talking about major releases only or any releases? Do we actually make a difference? Other than that, my thoughts

Re: Next wave of Providers (July 2022) in the making

2022-08-04 Thread Beck, Vincent
Hey Jarek, I’ll be working today on cleaning up deprecated modules from Amazon package. I’ll ping you when I have a PR ready (should be today). Thanks, Vincent From: Jarek Potiuk Reply-To: "dev@airflow.apache.org" Date: Thursday, August 4, 2022 at 11:28 AM To: "dev@airflow.apache.org" Subjec

[LAZY CONSENSUS] Create major version of FAB provider compatible only with Airflow 3

2024-11-06 Thread Beck, Vincent
Hi Airflow devs, I am calling a LAZY CONSENSUS to create a new major version of the fab provider that will only be compatible with Airflow 3. The reason why we need it is we are planning to make some breaking changes in the fab provider that will be incompatible with Airflow 2.X. Here are some

[LAZY CONSENSUS] AIP-82 - Create new interface `BaseEventTrigger`

2025-01-29 Thread Beck, Vincent
Hello everyone, During my AIP-82 demo at the last Airflow 3 dev call, I highlighted potential issues if users select an incorrect trigger when scheduling DAGs using event-driven scheduling. For example, using `S3KeyTrigger`, which fires whenever a specific file exists in an S3 bucket: ``` trig

Simple auth manager as default auth manager

2025-03-20 Thread Beck, Vincent
Hi everyone, I just merged https://github.com/apache/airflow/pull/47691 which sets SimpleAuthManager as the default auth manager in Airflow. If you pull the latest main branch, Airflow will no longer use the FAB auth Manager by default but instead use SimpleAuthManager. This is another step tow

Au revoir Flask

2025-04-07 Thread Beck, Vincent
Hi all, Just a quick FYI — PR #48457 (https://github.com/apache/airflow/pull/48457), which removes the Flask AppBuilder (FAB) provider from the preinstalled providers, has just been merged. This marks the successful completion of AIP-79! 🎉 Going forward, unless you explicitly install the FAB p

[DISCUSS] Auth backends

2025-02-28 Thread Beck, Vincent
Hi everyone, I would like to talk about auth backends. In Airflow 2, there are multiple options for authenticating REST API calls. These options are called auth backends (https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/api-authentication.html). The deployment m

[DISCUSS] Keycloak provider

2025-05-20 Thread Beck, Vincent
Hi all, I'd like to propose adding a new provider, Keycloak [1], to the collection of Apache Airflow providers. Keycloak is an open-source software product to allow single sign-on with identity and access management aimed at modern applications and services. The intent of this new provider wou

[DISCUSS] DB changes to support multi-team

2025-06-09 Thread Beck, Vincent
Hi everyone, As part of the multi-team AIP effort ([AIP-67][1]), I’m planning to begin work on updating the database schema to support multiple teams. Since this is a significant and potentially disruptive change, I wanted to first gather feedback on the proposed approach. ## Proposed plan 1.