mik-laj edited a comment on issue #9855: URL: https://github.com/apache/airflow/issues/9855#issuecomment-662062832
I thought about the extra option for a longer time and I don't think this will cover all cases. I think, we need `conflict-disposition` It should specifies the action that occurs if the variables/connection already exists. We should support the following values are supported: `OVERWRITE`: If the table variable/connection already exists, we should overwrites the data. `IGNORE`: If the table variable/connection already exists, we should skip this connection/variable. `RESTRICT`: If the variable/connection already exists, an exception is raised. The default value should be RESTRICT. Each command invocation should be atomic and only occurs if all changes is able to complete successfully (one transaction). Example: ``` airflow connection import /files/variables.json --merge-disposition=overwrite airflow connection import /files/variables.json --merge-disposition=ignore airflow connection import /files/variables.json --merge-disposition=restrict ``` ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
