je-enf opened a new issue, #67243:
URL: https://github.com/apache/airflow/issues/67243
### Under which category would you file this issue?
Airflow Core
### Apache Airflow version
3.2.1
### What happened and how to reproduce it?
Hello,
Consider the following code minimal example:
`from datetime import datetime, UTC
from airflow.providers.standard.operators.python import PythonOperator
from airflow import DAG
from airflow.sdk import Param, get_current_context
import logging
def parse_params():
ctx = get_current_context()
logging.error(ctx["params"])
with DAG(
dag_id="test_params",
start_date=datetime(2026, 1, 1, tzinfo=UTC),
params={
"my_param": Param(type="string", default="mystring"),
},
render_template_as_native_obj=True,
) as dag:
trigger_batch = PythonOperator(
task_id="parse_param",
python_callable=parse_params,
)
`
As this DAG contains a Param object, triggering it will always bring up the
parameters UI.
If I trigger it a first time with a given parameter for my_param, say 'foo',
and then select that run, click "Trigger again with this config" and change
'foo' to 'bar', the value in the params dict of the context still contains
'foo'.
### What you think should happen instead?
Either skip the parameters UI in that scenario or update the params with the
new given values.
### Operating System
debian
### Deployment
None
### Apache Airflow Provider(s)
_No response_
### Versions of Apache Airflow Providers
_No response_
### Official Helm Chart version
1.21.0 (latest released)
### Kubernetes Version
_No response_
### Helm Chart configuration
_No response_
### Docker Image customizations
_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]
