-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add config to disable the *deserialize* API flag
This flag is also *disabled* by default intentionally since it does not always work and every Airflow setup should review the payload manually to decide whether it's a good idea to enable the feature (it's usually not).
- Loading branch information
Showing
5 changed files
with
74 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
The ``xcomEntries`` API disables support for the ``deserialize`` flag by default | ||
|
||
For security reasons, the ``/dags/*/dagRuns/*/taskInstances/*/xcomEntries/*`` | ||
API endpoint now disables the ``deserialize`` option to deserialize arbitrary | ||
XCom values in the webserver. For backward compatibility, server admins may set | ||
the ``[api] enable_xcom_deserialize_support`` config to *True* to enable the | ||
flag and restore backward compatibility. | ||
|
||
However, it is strongly advised to **not** enable the feature, and perform | ||
deserialization at the client side instead. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters