@@ -133,7 +133,7 @@ The local OpenAPI UI can be found at [/api/v1/ui/](http://localhost:8008/api/v1/
...
@@ -133,7 +133,7 @@ The local OpenAPI UI can be found at [/api/v1/ui/](http://localhost:8008/api/v1/
The workflow for extending the API follows the **API First** approach. This means you have to edit the API at https://app.swaggerhub.com/apis/AURA-Engine/engine-api/, using the SwaggerHub web editor. Then download the `python-flask` server stubs, and replace & merge the existing generated sources in `src/aura_engine_api/rest`.
The workflow for extending the API follows the **API First** approach. This means you have to edit the API at https://app.swaggerhub.com/apis/AURA-Engine/engine-api/, using the SwaggerHub web editor. Then download the `python-flask` server stubs, and replace & merge the existing generated sources in `src/aura_engine_api/rest`.
All model files can usually be overwritten. Only controller and test classes need to undergo a merge action.
All model files can usually be overwritten. Only controller classes need to undergo a merge action. Test classes can be skipped.
Due to Swagger account limitations, you'll have to get in touch with the maintainer, when modifying the API specification. In the future it might be favorable to use a local OpenAPI editor and Codegen to generate the API artifacts.
Due to Swagger account limitations, you'll have to get in touch with the maintainer, when modifying the API specification. In the future it might be favorable to use a local OpenAPI editor and Codegen to generate the API artifacts.
