potiuk edited a comment on issue #17912: URL: https://github.com/apache/airflow/issues/17912#issuecomment-908501126
That would be a nice feature to allow yaml input - it should be entirely possible (and seems super easy). What we need is just a Dict form, and this is both yaml and json compatible. We could even actually even parse the entry with yaml parser rather with json and this would work pretty much out-of-the-box @msumit - maybe you can include it - every "valid json" is automatically also "valid yaml" by definition, so it should be rather easy (and maybe there should be an option to choose the "default" values generated in the field as either json or yaml -it could be a toggle and could be stored in cookies. The json-schema defintion can easily validate yaml input as well (we are doing it all the time in Airflow). When it comes to omegaconf, I think it's an overkill. We do not need to merge configurations - each DAG's configuration is separate from another, and they will never be "large and complex enough" to justify the interpolations, macros etc. I am not sure how omegaconf could be useful (though I do not know omegaconf - i got that impression after looking at the page, so maybe I do not get how it could be helpful. Maybe you can explain it @paantya and pass some example where you would find it useful )? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
