There is one model that need to be daily trained and updated through scheduled pipelines.
The new version of the model will also be updated in existing ACI REST API in staging instance.
Please note we don't want REST API to be created again, as there are applications using existing URL.
Also, if update failed, REST API to retain its state, not error out when called.
How to move this entire scenario to production deployment, so that in production once "deployed", pipelines can run seamlessly and update model and update existing production REST API with new model version?
Please note we don't want REST API to be created again, as there are applications using existing URL. Also, if update failed, REST API to retain its state, not error out when called.
Reasons for scenario
This is a extremely important business requirement and highly common scenario. There is no clear document|tutorial|guidelines around to do this.
Scenario Description
There is one model that need to be daily trained and updated through scheduled pipelines.
The new version of the model will also be updated in existing ACI REST API in staging instance.
Please note we don't want REST API to be created again, as there are applications using existing URL.
Also, if update failed, REST API to retain its state, not error out when called.
How to move this entire scenario to production deployment, so that in production once "deployed", pipelines can run seamlessly and update model and update existing production REST API with new model version?
Please note we don't want REST API to be created again, as there are applications using existing URL. Also, if update failed, REST API to retain its state, not error out when called.
Reasons for scenario
This is a extremely important business requirement and highly common scenario. There is no clear document|tutorial|guidelines around to do this.
Other Comments