potiuk commented on issue #14872: URL: https://github.com/apache/airflow/issues/14872#issuecomment-988771977
This shoudl be done outside of Helm or Image. Neither helm nor image lifecycle is good for that. Usually when you deploy Airflow you somehow needs to make sure the database is populated with the right configuration etc. Usually - if you need to re-create Airlfow deployment several time you employ some kind of "infrastructure as a service" approach - typically Terraform but there are ather possibilities. Preparing the initial database is the job of those tools. And since Airlfow is totally agnostic on how users are creating their "whole" deployments, you should simply make it in the way it is usually done in your organisation. We do not want to limit you in any way or suggest anything, because the space of possible solution is vast, and each organisation has their own standards on how this is done. -- 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]
