Updating Azure Functions Commands #1028
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed:
Python runtime version from 3.8 to 3.9 (azure function no longer supports 3.8)
Functions version was updated from 3 to 4 (you wont be able to create a new app function on version 3).
Added the --python flag at the end of the publishing command, infering the FUNCTIONS_WORKER_RUNTIME.
Here's some testing I made that backs the points above:
Alternatively, I have added variables instead of fixed values for container name and app name, given that it must be a unique name for each new instance and that can confuse people not familiar with how blob storage works.