marshall7m commented on issue #10454: URL: https://github.com/apache/airflow/issues/10454#issuecomment-1327989330
> I think it's more appropriate for https://airflow.apache.org/ecosystem/ > > You can release your own project and add a PR to make it part of the ecosysystem page. Cool for community, cool for you, but you will have to take the burden of managing people using it - which is also an opportunity - to build relations and business contacts. > > I think terraform - while popular and cool - is not something community would bank on and support on the community level. > > This is my personal opinion though. I like terraform and I know how useful it can be, but also I know it's very far from the "base" software/applicaton of Airflow. There are a number of opinionated decisions to make there, and I think it is difficult to make it iinto a "generic"/"reusable" solution (unlike Helm Chart of ours) so making it part of the "product" is not a good thing :) @potiuk Thanks for the link to the airflow ecosystem. I might consider adding it there. I see your point in regard to where Terraform stands within the Airflow community. Now that I think of it, it would be interesting if there was a solution but reversed. I'm thinking if there was a Terraform Airflow provider that allowed DAGs to be defined within Terraform files so that Terraform resources could be directly interpolated into DAG operator configurations. Although it seems like that would require some magic to sync the updated DAG to the hosted Airflow environment... Anyhow thanks for the quick feedback! -- 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]
