PoC of AIP-69 - A first task can be called remote #40224
Conversation
boring-cyborg
bot
added
area:dev-tools
area:Executors-core
There was a problem hiding this comment.
Note: This change is needed allowing to re-route the Internal API calls to another endpoint (Assuming: Remote Worker API should be HTTPS (not HTTP) and needs to be exposed Internet-Facing. (App GW, Protection different than internal API)
There was a problem hiding this comment.
This is a temporary script for development testing to start the remote worker.
Note that mainly it is used to drop all DB connection information to ensure that all backend calls must be made via HTTP API.
There was a problem hiding this comment.
Note: This extension is needed to allow new Pydantic class mappings from Remote Provider Package to be registered - allowing to leverage AIP-44 RPC call logic with non-code model classes
jscheffl
force-pushed
the
feature/aip-69-poc
branch
3 times, most recently
from
10c46e6 to
9ec0db9
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
2 times, most recently
from
6d3960c to
a676ff3
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
from
a676ff3 to
2c177c4
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
from
2c177c4 to
b435658
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
5 times, most recently
from
732068b to
92e171f
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
6 times, most recently
from
e77da34 to
1e51a55
Compare
jscheffl
force-pushed
the
feature/aip-69-poc
branch
from
9b004a8 to
15c3dc4
Compare
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
github-actions
bot
added
the
stale
|
Yeah, cool. Stale... but code "almost" is on main... closing but keeping as reference of progress. |
This PR is a DRAFT to further discuss technical details on AIP-69 direction. DO NOT MERGE - but please feedback on it.
Please treat this as a PoC, it is only partly working. It can be used to distribute the first task but a lot of core required functions to make a MVP are missing. Status of implementation is tracked in
airflow/providers/remote/TODO.mdin this PR.If you want to test it you can:
breeze start-airflow --python 3.12 --load-example-dags --backend postgres --executor RemoteExecutor --answer yairflow/providers/remote/_start_remote_worker.shexample_python_operator. Wohoo!Based on progress and time I will sometimes rebase and push changes to this branch. But it will not be something that will be review-able.
I will not add any migration logic in case of updates for the additional tables in DB Scheme. If I update the draft PR and DB schema changes, DB might need to be reset. Of course migration support would need to be added before a "real" release.