Re: About the project support in Airflow
My suggestion would be to deploy airflow per project. You could even use airflow to manage your ci/cd pipeline.
Sent from my iPhone
> On 24 Apr 2018, at 18:33, Maxime Beauchemin <maximebeauchemin@xxxxxxxxx> wrote:
> People have been talking about namespacing DAGs in the past. I'd recommend
> using tags (many to many) instead of categories/projects (one to many).
> It should be fairly easy to add this feature. One question is whether tags
> are defined as code or in the UI/db only.
>> On Tue, Apr 24, 2018 at 1:48 AM, Song Liu <songliu@xxxxxxxxxxx> wrote:
>> Basically the DAGs are created for a project purpose, so if I have many
>> different projects, will the Airflow support the Project concept and
>> organize them separately ?
>> Is this a known requirement or any plan for this already ?