openwhisk-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [openwhisk] style95 commented on issue #4580: [Discussion] Action Versioning
Date Fri, 09 Aug 2019 06:14:23 GMT
style95 commented on issue #4580: [Discussion] Action Versioning
   Let me share some excerpts from the discussion threads on Slack with @rabbah and @chetanmeh.
   > chetanm 1:03 PM
   Internally model does has support for version (as a SemVer) but its not currently used
much apart form helping in distinguishing changed entities
   > rr 1:06 PM
   There’s a history of discussions around versioning in the issues on GitHub. iirc it comes
down to does the system enforce semver or leave it to the user. To mimic aws lambda versions
could be done a user level for the most part, and the api would allow an alias for “latest”
(by user level I mean you make it part of the action name)
   > chetanm Yesterday at 1:12 PM
   This scheme also leaves gc of old action to user. Worst cases it can bloat up storage a
bit … so for not that big issue
   > rr  1 day ago
   Indeed. At user level means you have to clean up at user level also.
   > chetanm  1 day ago
   and currently there is no quota on user storage. So for now user has no incentive to clean
   > rr  1 day ago
   yep that’s true
   > style95  1 day ago
   I think we can define some default limits such as 10 recent versions though there ist still
no quota in a namespace. (edited)
   > style95  1 day ago
   Users can benefit from SCMs to manage the versioning of their actions, but I think it would
be much useful if the platform itself supports the versioning.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message