metalshanked opened a new issue, #53901:
URL: https://github.com/apache/airflow/issues/53901
### Description
The Airflow REST API is a critical component for programmatic interaction
and management. While it supports PATCH requests for updating resources, it
lacks a standard update_mask field. This pattern, common in modern APIs (and
even documented as a convention for Airflow's own Python client), tells the
server precisely which fields to modify. Without it, the server must infer the
fields to update from the request body, which can be ambiguous and lead to
unintended side effects if a client sends a full object representation instead
of just the changed fields.
### Use case/motivation
For a target API endpoint (e.g., PATCH /connections/{connection_id}), modify
the backend Flask view to accept an update_mask query parameter.
The update_mask would be a comma-separated string of field names (e.g.,
update_mask=login,password).
The API logic would parse this mask and iterate through the specified
fields, applying only those changes from the request body to the database
model. Any fields present in the request body but not in the update_mask would
be ignored.
Update the OpenAPI specification for the Airflow API to document this new
parameter for all relevant PATCH endpoints.
### Related issues
_No response_
### Are you willing to submit a 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]
