> content to the dag_code table.
>
> One obvious downside to this approach is that whenever I upgrade airflow I
> have to double check in staging that my hack still works. But the function
> I patch is super simple and my change is like 4 extra lines of code, so I
> don't mind it
cution in future versions (i.e. 2.2) so we can't do that.
>
> -ash
>
> On Sat, Aug 21 2021 at 09:50:57 +0530, Siddharth VP
> wrote:
>
> Yes per my commit linked above, it would be the yaml file that is shown in
> the webserver code view (because the fileloc field p
dding better support for parametrized DAGs and
>> dynamic DAGs using JSON/YAML dataformats
>>
>>
>>
>> Airflow DAGS are Python code.This is a very basic assumption - which is
>> not likely to change. Ever.
>>
>>
>>
>> And we are working on
Would like to know your thoughts on this. Thanks!
Siddharth VP
