-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable file name #1323
Configurable file name #1323
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #1323 +/- ##
==========================================
+ Coverage 85.11% 85.84% +0.72%
==========================================
Files 35 35
Lines 1955 1971 +16
Branches 370 371 +1
==========================================
+ Hits 1664 1692 +28
+ Misses 217 210 -7
+ Partials 74 69 -5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…-worker into hallvictoria/configurable_file_name
…-worker into hallvictoria/configurable_file_name
…com/Azure/azure-functions-python-worker into hallvictoria/configurable_file_name
…-worker into hallvictoria/configurable_file_name
…com/Azure/azure-functions-python-worker into hallvictoria/configurable_file_name
|
||
if not os.path.exists(function_path): | ||
# Fallback to legacy model | ||
logger.info("%s does not exist. " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this necessary to log in general? If this log can be merged in the earlier log itself?
Description
The Python worker reads the function app entry point from an app setting called
PYTHON_SCRIPT_FILE_NAME
. The default value for this setting will still be "function_app.py". Customers can signal to the worker to read from a file not called "function_app.py" by setting this variable to the new name of their file.Added unit and e2e tests for this app setting by creating a function app file not called "function_app.py" and testing it.
Also added unit tests for 2 invalid V2 app scenarios: no top level function app instances and no inputs
Fixes #https://github.com/Azure/azure-functions-pyfx-planning/issues/72
PR information
Quality of Code and Contribution Guidelines