-
Notifications
You must be signed in to change notification settings - Fork 32
🐛 Fixes WEBSERVER_FUNCTIONS to run in development deploys
#7687
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
🐛 Fixes WEBSERVER_FUNCTIONS to run in development deploys
#7687
Conversation
WEBSERVER_FUNCTIONS as development featureWEBSERVER_FUNCTIONS to run in development deploys
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7687 +/- ##
==========================================
- Coverage 87.45% 83.99% -3.46%
==========================================
Files 1802 694 -1108
Lines 70121 32942 -37179
Branches 1137 170 -967
==========================================
- Hits 61323 27671 -33652
+ Misses 8488 5214 -3274
+ Partials 310 57 -253
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
matusdrobuliak66
left a comment
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.
👍
|
@mergify queue |
🟠 Waiting for conditions to match
|
wvangeit
left a comment
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.
Thx
|



What do these changes do?
Fixes configuration of
WEBSERVER_FUNCTIONSWEBSERVER_FUNCTIONSwas incorrectly configured: it was marked as_X_FEATURE_UNDER_DEVELOPMENT, which is correct, but it was also explicitly set toFalse.The
_X_FEATURE_UNDER_DEVELOPMENTflag is meant to disable features in production while keeping the actuall setting in development. Explicitly settingWEBSERVER_FUNCTIONS=Falsewill always (either development or production) keep this feature disabled.WEBSERVER_FUNCTIONSsuch that it only runs ifWEBSERVER_DEV_FEATURES_ENABLED=Trueand otherwise it is disabled.Side note:
WEBSERVER_DEV_FEATURES_ENABLEDenvironment variable is INDEED misleading—likely the result of incremental changes without a full review of the underlying logic.WEBSERVER_DEV_FEATURES_ENABLED: Enforce Automatic Disabling of Under-Development Plugins in Production #7688 and improve this mechanism.Related issue/s
How to test
Dev-ops