Isnt there a better way to wrap REST APIs in a client?

[mahiki]

I think there might even be a julia package that does this. Right now I am hard-coding the block structure from existing blocks. Potential support could be:

• creating blocks, deployments
• creating flows, tasks

Again, Prefect had a blurb that they were working on a Julia SDK.

[mahiki]

Yes, there are established code-generation techniques to automatically create the REST API client package.

AWS.jl design document describes one approach, covers all AWS services.

Swagger.jl (OpenAPI) packge is a code generator plugin to create your own client library. Its Java based.

So... yes there is a right way, but they are a heavy lift. Maybe the Swagger way is actually pretty easy -- not ready to put effort into learning it just now.

So far the hand rolled small-scale is the best approach. I only need a small set of API calls to run the Julia part of my deployed jobs. Don't need to deploy or define flows in Julia -- just need the following:

• access to block information
• logging from Julia process

Leaving this issue open for now, but likely will close as out of scop.

[mahiki]

Notes from slack, other examples of API wrapping:

Trello.jl
Airtable.jl

They say avoid AWS.jl as an example, lot of design driven by the huge size of the API.

[mahiki]

New one that is very clean example, MatterMost.jl. OpenAPI generated interface.

So what else is needed for writing Julia code that orchestrates with Prefect?

• @flow decorators functionality easy in julia, even macro-style
• prefect cli, it works the same? I suppose so. And running a flow from file is julia --file=... type of thing. The worker is local process, the observability comes from the @flow macroized calls from the julia script.