gbonazzoli opened a new issue #20579:
URL: https://github.com/apache/airflow/issues/20579


   ### Apache Airflow version
   
   2.2.3 (latest released)
   
   ### What happened
   
   When issuing the following command:
   
   `airflow dags trigger 'VMWARE_BACKUP'  --conf '{"VM_NAME":"psfiplb1"}'`
   
   the system replays with:
   
   ```
   
/usr/local/lib/python3.8/dist-packages/airflow/api/common/experimental/trigger_dag.py:85
 DeprecationWarning: Calling `DAG.create_dagrun()` without an explicit data 
interval is deprecated
   Created <DagRun VMWARE_BACKUP @ 2021-12-31T00:00:00+00:00: 
manual__2021-12-31T00:00:00+00:00, externally triggered: True>
   ```
   
   ### What you expected to happen
   
   I have no other switch parameter to choose for avoiding the deprecation 
warning.
   
   My concern is about what will happen to the command when the deprecation 
will transforms itself in an error.
   
   ### How to reproduce
   
   _No response_
   
   ### Operating System
   
   Ubuntu 20.04.3 LTS
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-celery==2.1.0
   apache-airflow-providers-ftp==2.0.1
   apache-airflow-providers-http==2.0.1
   apache-airflow-providers-imap==2.0.1
   apache-airflow-providers-microsoft-mssql==2.0.1
   apache-airflow-providers-microsoft-winrm==2.0.1
   apache-airflow-providers-openfaas==2.0.0
   apache-airflow-providers-oracle==2.0.1
   apache-airflow-providers-samba==3.0.1
   apache-airflow-providers-sftp==2.3.0
   apache-airflow-providers-sqlite==2.0.1
   apache-airflow-providers-ssh==2.3.0
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   Airflow inside an LXD continer
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]


Reply via email to