aqueductcore

aqueductcore copied to clipboard

API enhancement request

1

**Describe the bug** It's a request to modify API fields for better simplicity and common sense alignment. **Current API** 1- The unique identifier which is referred to by the name...

safeamiiir

Now we have the requirements captured for experiments data import/export feature, the functional specification needs to be documented as a guideline for the development of this feature.

samiralavi

Plugin execution may take time. To track plugin execution and be able to address plugin execution history, we should be able to execute plugins as jobs. This includes: 1. Running...

str-anger

`addTagToExperiment` mutation only accepts a single tag as an argument. If the API users want to add multiple tags in an atomic way, it is not possible. (`updateExperiment` mutation can...

samiralavi

After collection of the parameters and building an interface we have to pass these values to a server endpoint and expect it to return results. Results will consist of generic...

str-anger

The screen is generated according to endpoint declaration and builds a form to populate with values. To start these might be: - Experiment dropdown (with search) -- PROBABLY if we...

str-anger

there is a screen which takes plugin list from the endpoint and represents them together with their functions. Probably this will be a 2-level tree-like structure: each plugin has a...

str-anger

samiralavi

When/if Airflow is supported in Aqueduct, plugins should work transparently as Airflow nodes.

str-anger

str-anger