-
Notifications
You must be signed in to change notification settings - Fork 32
🔨 Exposes WEBSERVER_FUNCTION env to wb-api-server simcore service ⚠️
#7751
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
🔨 Exposes WEBSERVER_FUNCTION env to wb-api-server simcore service ⚠️
#7751
Conversation
wb-api-server simcore servicewb-api-server simcore service ⚠️
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 @pcrespov
|
@mergify queue |
🟠 Waiting for conditions to match
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7751 +/- ##
==========================================
+ Coverage 87.05% 87.36% +0.30%
==========================================
Files 1804 1834 +30
Lines 69314 71266 +1952
Branches 1214 1214
==========================================
+ Hits 60341 62261 +1920
- Misses 8630 8662 +32
Partials 343 343
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
e04f212 to
8be9553
Compare
…VER_FUNCTIONS and WEBSERVER_NOTIFICATIONS in various test fixtures
8be9553 to
3dbd49e
Compare
|



What do these changes do?
wb-api-serversimcore service. Everywhere else is must be always disabledRelated issue/s
How to test
Dev-ops
These are the values of
WEBSERVER_FUNCTIONset for each deploy (@wvangeit will change these in the future according to their release workflow):