potiuk commented on issue #19688: URL: https://github.com/apache/airflow/issues/19688#issuecomment-974008306
Some more context: We had a long discussion with Matthew in the past on why it makes no sense to have it - basically if we do want to make it works, we need to get "terraform-like" desired state described. I.e. when we install a new version of chart, we should describe what is the "final" state of the DB configuration we want to achieve, rather than what actions to execute. Otherwise we fall into all the kind of problems on how to merge changes that were manually done in the database - answering questions like "should we keeep existing values, or override them". For me this is something that is a "terraform" (or other kind of deployment you do) and not "helm" job - and helm should only really create and update structure of the DB but never insert/modify data in the DB. at least that was my opinion and result of the discussion so far :). -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
