feat: add concurrency flag to create and update#316
Conversation
Codecov Report
@@ Coverage Diff @@
## master #316 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 66 66
Lines 1749 1752 +3
Branches 367 369 +2
=========================================
+ Hits 1749 1752 +3
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
pru55e11
left a comment
There was a problem hiding this comment.
overall looks good to me. How'd you come up with the max 500 concurrency? Should we load test this and adjust as needed?
|
lgtm! Do we have a similar test in the app plugin for deploying from app.config.yaml? |
|
I don't think we do this sort of validation in the app plugin, so there's no similar tests Agreed on the server side enforcement... Let me spend some time seeing if each of the min/max errors coming back from openwhisk are sufficient and we can remove the client side checking |
|
Yea I think the server responses seem fine, let me remove the client side checking here and then make another pr for the other flags in this command Max exceeded Min exceeded |
|
Client side validation removed. Also opened a new PR doing this for other commands: #317 |
Description
Add a new flag for setting
concurrencyof actionsDefault, min, and max taken from Runtime System Settings
Motivation and Context
Trying to set concurrency of a blackbox action, which can't be managed with app.config.yaml
How Has This Been Tested?
Locally linked plugin,
npm run testScreenshots (if appropriate):
Types of changes
Checklist: