Closed natke closed 7 months ago
@natke Thanks for your feedback! We will investigate and update as appropriate.
@natke Thank you for bringing this to our attention. I've delegated this to content author @dem108, who will review it and offer their insightful opinions.
@dem108 Could you please review add comments on this, update as appropriate.
Thanks for your feedback @natke . Local deployment does have limitation that it cannot use model or environment registered in the workspace, but only can use model/environment from local. This is basically because local deployment would run locally isolated from cloud. This is described here: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-deploy-online-endpoints?view=azureml-api-2&tabs=azure-cli#:~:text=Local%20endpoints%20have%20the%20following%20limitations
We recognize it only mentions local model. Let us follow up and update it to reflect on environment as well.
Thanks!
The article is updated to mention environment as well. Let us close this, but feel free to comment further.
Thank you for making the update. So do I conclude from this that I need a different deployment yml file for local and cloud deployments?
Thank you for making the update. So do I conclude from this that I need a different deployment yml file for local and cloud deployments?
Not necessarily. You can use the same file but override as needed by using --set
.
It's great to have the tools to develop and debug endpoints locally. The document is a little light on differences between the paths that you use for environments and models locally vs in the cloud. Is there a single configuration that can be used for both?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.