jscheffl commented on PR #54296: URL: https://github.com/apache/airflow/pull/54296#issuecomment-3172138268
> > There's no need for us remove import. Rename it to bulk-create if you want, but why remove it? > > I think if we leave it, we have to explain how to create a good "export" file to be able to "import" - we could explain in detail that you need to run "export" using "cli" command rather than airflowctl. It would be quite confusing to see "import" option and no explanation on how to create the file. > > I think we could leave import if we explain that - at least for now we remove export, and explain the relationship to "airflow" CLI, but I find it fairly confusing. > > Or do you think @ashb that people will be preparing such import files manually or in other ways? I find it quite improbable, and if we expect it to happen then we likely need to describe the exact format of the import file so that they can do it (but again - I do not find it too likely for users to do it - they would rather use "airflow connection export" after logging in to the airflow pod/contianer/venv - and we should at the very least tell it ito them? > > Or am I missing something? I see and agree to both of your statements. But if we want admins in future to use `airflowctl` as well might be "handy" similar like `kubectl apply -f ...` ... and importing is perfectly secure. Yeah might be confusing first-place but is good if you can also "from remote" import? Better than forcing getting your definitions on the server side to run import on CLI only. -- 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]
