atul-astronomer opened a new issue, #47920:
URL: https://github.com/apache/airflow/issues/47920

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Setting a variable in Dag is failing due to 'Direct database access via the 
ORM is not allowed in Airflow 3.0'
   
   <img width="931" alt="Image" 
src="https://github.com/user-attachments/assets/eb756885-9eef-4d75-a798-36f451ba3d19";
 />
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   Have the below dag in dags folder, you will get import error.
   
   ```python
   from datetime import datetime
   
   from airflow.providers.standard.operators.bash import BashOperator
   from airflow.models import Variable
   
   from airflow import DAG
   
   my_var = Variable.set("param_variable", 10)
   
   dag = DAG(
       'test_api_dag',
       start_date=datetime(2025, 3, 1, 3, 28, 0),
       # # schedule=timedelta(days=1),
       schedule='@daily',
       is_paused_upon_creation=False
   )
   
   hello_task = BashOperator(
       task_id='test_task',
       bash_command='echo "Hello World from Airflow!"',
       do_xcom_push = True,
       dag=dag,
   )
   
   hello_task
   
   ``` 
   
   ### Operating System
   
   Linux
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### 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