This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
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.
Closes #45.
The previous Hotfix only addressed the surface-level issue of the
az webapp up
command not working. I naively did not properly manually test the deployed app, and turns out it was not running correctly at all: Azure App Services build their environments from therequirements.txt
file (unsurprisingly) and as such the pip requirements must be placed into that file.This PR includes changes to the environment locking script to seperate the conda and pip package versions between
environment.yml
andrequirements.txt
respectively, as well as pinningmsrest==0.6.21
to circumvent certain incompatibilities as discussed in this thread.