Tracking: Missing workflow in API

DanielVoogsgerd commented 2 weeks ago

Since the introduction of the policy reasoner, various functions need to provide a workflow to the registry in order to retrieve data. The problem is that some interfaces cannot infer this information with the current API. Therefore, the API has to change. This is a tracking issue for the interfaces that still need to change.

[ ] brane-cli: download_result
[ ] brane-cli-c: vm_process
[ ] brane-cli: download_data

All of these should be fixed before we can create a 4.0.0 release, download_result needs to be fixed for the basic functionality of datasets to work again.

Lut99 commented 1 week ago

API -> brane-api?

DanielVoogsgerd commented 1 week ago

API -> brane-api?

No, just the abstract term. The brane-reg download-data api requires a workflow. If you look at the callers of that api and then bubble that requirement up the call stack you basically end up at these user entrypoints/api-calls where we don't prompt the user for the required information to complete the request now that we have the policy reasoner.

So in order to resolve this, we have to either require or infer that data so we can make a valid brane-reg api call.

epi-project / brane

Tracking: Missing workflow in API #195