• Home
• Core Concepts
• Params

Params

Params enable you to provide runtime configuration to tasks. You can configure default Params in your DAG code and supply additional Params, or overwrite Param values, at runtime when you trigger a DAG. Param values are validated with JSON Schema. For scheduled DAG runs, default Param values are used.

Also defined Params are used to render a nice UI when triggering manually. When you trigger a DAG manually, you can modify its Params before the dagrun starts. If the user-supplied values don’t pass validation, Airflow shows a warning instead of creating the dagrun.

DAG-level Params

To add Params to a DAG, initialize it with the params kwarg. Use a dictionary that maps Param names to either a Param or an object indicating the parameter’s default value.

 from airflow import DAG
 from airflow.models.param import Param

 with DAG(
     "the_dag",
     params={
         "x": Param(5, type="integer", minimum=3),
         "my_int_param": 6
     },
 ):

Task-level Params

You can also add Params to individual tasks.

def print_my_int_param(params):
  print(params.my_int_param)

PythonOperator(
    task_id="print_my_int_param",
    params={"my_int_param": 10},
    python_callable=print_my_int_param,
)

Task-level params take precedence over DAG-level params, and user-supplied params (when triggering the DAG) take precedence over task-level params.

Referencing Params in a Task

Params can be referenced in templated strings under params. For example:

 PythonOperator(
     task_id="from_template",
     op_args=[
         "{{ params.my_int_param + 10 }}",
     ],
     python_callable=(
         lambda my_int_param: print(my_int_param)
     ),
 )

Even though Params can use a variety of types, the default behavior of templates is to provide your task with a string. You can change this by setting render_template_as_native_obj=True while initializing the DAG.

 with DAG(
     "the_dag",
     params={"my_int_param": Param(5, type="integer", minimum=3)},
     render_template_as_native_obj=True
 ):

This way, the Param’s type is respected when it’s provided to your task:

# prints <class 'str'> by default
# prints <class 'int'> if render_template_as_native_obj=True
PythonOperator(
    task_id="template_type",
    op_args=[
        "{{ params.my_int_param }}",
    ],
    python_callable=(
        lambda my_int_param: print(type(my_int_param))
    ),
)

Another way to access your param is via a task’s context kwarg.

 def print_my_int_param(**context):
     print(context["params"]["my_int_param"])

 PythonOperator(
     task_id="print_my_int_param",
     python_callable=print_my_int_param,
     params={"my_int_param": 12345},
 )

JSON Schema Validation

Param makes use of JSON Schema, so you can use the full JSON Schema specifications mentioned at https://json-schema.org/draft/2020-12/json-schema-validation.html to define Param objects.

with DAG(
    "my_dag",
    params={
        # an int with a default value
        "my_int_param": Param(10, type="integer", minimum=0, maximum=20),

        # a required param which can be of multiple types
        # a param must have a default value
        "multi_type_param": Param(5, type=["null", "number", "string"]),

        # an enum param, must be one of three values
        "enum_param": Param("foo", enum=["foo", "bar", 42]),

        # a param which uses json-schema formatting
        "email": Param(
            default="example@example.com",
            type="string",
            format="idn-email",
            minLength=5,
            maxLength=255,
        ),
    },
):

Note

If schedule is defined for a DAG, params with defaults must be valid. This is validated during DAG parsing. If schedule=None then params are not validated during DAG parsing but before triggering a DAG. This is useful in cases where the DAG author does not want to provide defaults but wants to force users provide valid parameters at time of trigger.

Note

As of now, for security reasons, one can not use Param objects derived out of custom classes. We are planning to have a registration system for custom Param classes, just like we’ve for Operator ExtraLinks.

Use Params to Provide a Trigger UI Form

New in version 2.6.0.

DAG level params are used to render a user friendly trigger form. This form is provided when a user clicks on the “Trigger DAG” button.

The Trigger UI Form is rendered based on the pre-defined DAG Params. If the DAG has no params defined, the trigger form is skipped. The form elements can be defined with the Param class and attributes define how a form field is displayed.

The following features are supported in the Trigger UI Form:

• Direct scalar values (boolean, int, string, lists, dicts) from top-level DAG params are auto-boxed into Param objects. From the native Python data type the type attribute is auto detected. So these simple types render to a corresponding field type. The name of the parameter is used as label and no further validation is made, all values are treated as optional.

• If you use the Param class as definition of the parameter value, the following attributes can be added:

  • The Param attribute title is used to render the form field label of the entry box. If no title is defined the parameter name/key is used instead.

  • The Param attribute description is rendered below an entry field as help text in gray color. If you want to provide special formatting or links you need to use the Param attribute description_md. See tutorial DAG example_params_ui_tutorial for an example.

  • The Param attribute type influences how a field is rendered. The following types are supported:

    Param type	Form element type	Additional supported attributes	Example
    string	Generates a single-line text box to edit text.	minLength: Minimum text length maxLength: Maximum text length format="date": Generate a date-picker with calendar pop-up format="date-time": Generate a date and time-picker with calendar pop-up format="time": Generate a time-picker enum=["a", "b", "c"]: Generates a drop-down select list for scalar values. As of JSON validation, a value must be selected or the field must be marked as optional explicit. See also details inside the JSON Schema Description for Enum. values_display={"a": "Alpha", "b": "Beta"}: For select drop-downs generated via enum you can add the attribute values_display with a dict and map data values to display labels. examples=["One", "Two", "Three"]: If you want to present proposals for values (not restricting the user to a fixed enum as above) you can make use of examples which is a list of items. Also see further JSON Schema string type validation options which are checked before DAG trigger in the backend.	Param("default", type="string", maxLength=10) Param(f"{datetime.date.today()}", type="string", format="date")
    number or integer	Generates a field which restricts adding numeric values only. The HTML browser typically also adds a spinner on the right side to increase or decrease the value. integer only permits int numbers, number allows also fractional values.	minimum: Minimum number value maximum: Maximum number value Also see further JSON Schema numeric type validation options which are checked before DAG trigger in the backend.	Param(42, type="integer", minimum=14, multipleOf=7)
    boolean	Generates a toggle button to be used as True or False.	none.	Param(True, type="boolean")
    array	Generates a HTML multi line text field, every line edited will be made into a string array as value.	If you add the attribute examples with a list, a multi-value select option will be generated instead of a free text field. values_display={"a": "Alpha", "b": "Beta"}: For multi-value selects examples you can add the attribute values_display with a dict and map data values to display labels. If you add the attribute items, a JSON entry field will be generated for more array types and additional type validation as described in JSON Schema Array Items.	Param(["a", "b", "c"], type="array") Param(["two", "three"], type="array", examples=["one", "two", "three", "four", "five"])
    object	Generates a JSON entry field with text validation.	The HTML form does only validate the syntax of the JSON input. In order to validate the content for specific structures take a look to the JSON Schema Object details.	Param({"key": "value"}, type=["object", "null"])
    null	Specifies that no content is expected. Standalone this does not make much sense but it is useful for type combinations like type=["null", "string"] as the type attribute also accepts a list of types. Per default if you specify a type, a field will be made required with input - because of JSON validation. If you want to have a field value being added optional only, you must allow JSON schema validation allowing null values.		Param(None, type=["null", "string"])

• If a form field is left empty, it is passed as None value to the params dict.

• Form fields are rendered in the order of definition of params in the DAG.

• If you want to add sections to the Form, add the attribute section to each field. The text will be used as section label. Fields w/o section will be rendered in the default area. Additional sections will be collapsed per default.

• If you want to have params not being displayed, use the const attribute. These Params will be submitted but hidden in the Form. The const value must match the default value to pass JSON Schema validation.

• On the bottom of the form the generated JSON configuration can be expanded. If you want to change values manually, the JSON configuration can be adjusted. Changes are overridden when form fields change.

• To pre-populate values in the form when publishing a link to the trigger form you can call the trigger URL /dags/<dag_name>/trigger and add query parameter to the URL in the form name=value, for example /dags/example_params_ui_tutorial/trigger?required_field=some%20text. To pre-define the run id of the DAG run, use the URL parameter run_id.

Note

If the field is required the default value must be valid according to the schema as well. If the DAG is defined with schedule=None the parameter value validation is made at time of trigger.

For examples also please take a look to two example DAGs provided: example_params_trigger_ui and example_params_ui_tutorial.

New in version 2.7.0: The trigger form can also be forced to be displayed also if no params are defined using the configuration switch webserver.show_trigger_form_if_no_params.

Changed in version 2.8.0: By default custom HTML is not allowed to prevent injection of scripts or other malicious HTML code. If you trust your DAG authors you can change the trust level of parameter descriptions to allow raw HTML by setting the configuration entry webserver.allow_raw_html_descriptions to True. With the default setting all HTML will be displayed as plain text. This relates to the previous feature to enable rich formatting with the attribute description_html which is now super-seeded with the attribute description_md. Custom form elements using the attribute custom_html_form allow a DAG author to specify raw HTML form templates. These custom HTML form elements are deprecated as of version 2.8.0.

Disabling Runtime Param Modification

The ability to update params while triggering a DAG depends on the flag core.dag_run_conf_overrides_params. Setting this config to False will effectively turn your default params into constants.

Previous Next

Was this entry helpful?