Dependencies
When a driver is loaded into Engine, it becomes a dependency. Dependencies are available as the blueprint from which modules are created. The /dependencies
endpoint provide methods to discover, load and update these. For more on the role the drivers play, see:
Model
Search
GET
https://example.com/api/control/dependencies
List or search for loaded dependencies.
Query Parameters
Queries default to searching for any of the entered terms (words). A small query language provides the ability to structure complex queries.
Management
Create
POST
https://example.com/api/control/dependencies
Defines a new dependency. The driver this references must be available on the engine nodes running this instance of Engine. Available drivers can be listed by using the discovery endpoint.
Request Body
Retrieve
GET
https://example.com/api/control/dependencies/{id}
Gets dependency information
Path Parameters
Update
PUT
https://example.com/api/control/dependencies/{id}
Updates dependency metadata.
Path Parameters
Request Body
Delete
DELETE
https://example.com/api/control/dependencies/{id}
Unloads a driver.
Path Parameters
Interaction
Reload
POST
https://example.com/api/control/dependencies/{id}/reload
Live reloads the latest version of the driver code and updates all modules using this.
Path Parameters
Last updated