Migrates using Image to using Environment in the o16n notebook #964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Creating and deploying a ContainerImage is soon-to-be deprecated functionality inside of AzureML service.
The new recommended flow is instead to prepare an Environment object that contains your Pip/Conda requirements and simply include this in your InferenceConfiguration to be supplied in a Model.deploy() call.
This speeds up image build and service deployment time, and allows subsequent service deployments to leverage existing prepared Environment images.
Related Issues
#962
Checklist: