Uh oh!
There was an error while loading. Please reload this page.
AIP-84 Migrate patch a connection to FastAPI API - #43102
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
f33126e to
e58dae7CompareUh oh!
There was an error while loading. Please reload this page.
94bfe26 to
fa62ca2Comparefa62ca2 to
104d004Compare
pierrejeambrun
left a comment
There was a problem hiding this comment.
I think we should also make consistant the behavior for PATCH regarding None value.
Here when there is a mask you take them. And when there is no mask, you filter them out.
I did something different for Pool which I think can be extented. When there is a mask, same thing, we use values. When there is no mask, we validate that the payload is valide by it's own, i.e it's a valid db entity by its own, and we use everything. (none or not).
The idea is to allow someone to not specify mask and reset some fields to None if needed.
I just pushed one commit to remove a remnent of old code |
104d004 to
f4c90ddCompareI think we have the same issue here, we cannot |
bugraoz93
commented
Oct 28, 2024
I totally missed this one, thanks for the changes! :) |
bugraoz93
commented
Oct 28, 2024
I think I looked from the lazy path when no parameter, no value to you :) Saw your changes. Looks good and makes sense! I agree, we should have a common approach for common methods because what we are doing at the end is pretty similar. |
pierrejeambrun
commented
Oct 29, 2024
For 'common' behavior of null values we can do that in another PR. That is not really specific to this one. I think we can just handle the 'password', then merge it, maybe you can take care of making all |
bugraoz93
commented
Oct 29, 2024
Yeap, it sounds perfect! I am going to take care of that after finishing the |
pierrejeambrun
left a comment
There was a problem hiding this comment.
We need to handle the password
Uh oh!
There was an error while loading. Please reload this page.
2b85e78 to
0b67aaeCompareUh oh!
There was an error while loading. Please reload this page.
3ea9442 to
591657dCompare591657d to
d26497aComparebugraoz93
commented
Nov 4, 2024
Tests should be fixed in #43654. |
pierrejeambrun
left a comment
There was a problem hiding this comment.
Looking good.
Need rebasing to fix conflicts, we can merge after.
…ameter Field default value for backward compatibility
…on for backward compat and fix for variables serialisation won't update val in setattr()
…date_mask breaking change
d26497a to
7c19e96Comparebugraoz93
commented
Nov 5, 2024
Many thanks for rebasing and merging the other PR! You saved me from facing the conflict twice 🙏 Rebased. |
* Migrate Patch Connection endpoint to FastAPI and Include Optional parameter Field default value for backward compatibility * Make all tests parametrized * Make UpdateMask Annotated for Patch endpoints, update the serialisation for backward compat and fix for variables serialisation won't update val in setattr() * Merge duplicate imports * Revert update_mask to explode true and include significant.rst for update_mask breaking change * Amend update_mask as array * generalize handling of list query parameters in newsfragment * Include password field * Include password to response and tests, rebase and rerun pre-commit * Fix copy&paste mistakes for method and naming * Convert redact_password to agreed approach, rebase and pre-commits * Include new exception doc generation * Run pre-commit after rebase
closes: #42592.
Include, making fields nullable for patch endpoints for backward compatibility.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.