RE: Dangers of renaming and removing runtime kinds

2019-09-17 Thread Sven Lange-Last
Hello Tyson, I think your proposal makes perfect sense. It would be very helpful for adopters to have a kind of operator's guide. Most of the documentation is very developer centric and we see a lot of questions in the Openwhisk Slack asking for guidance when deploying the system. There are

Re: Dangers of renaming and removing runtime kinds

2019-09-17 Thread Tyson Norris
I think the PR is a good start, but I also think upgrading OpenWhisk is a hazardous area that has broader scope that operators need to consider when running OpenWhisk with any custom configuration (and nobody should probably run with default config, but I guess technically it would be

Re: Dangers of renaming and removing runtime kinds

2019-09-16 Thread Rodric Rabbah
I don't think there is actually a distinction between the two paths in deserialize(). The try path throws the exception inside docReader.read() whereas in the catch, the exception is deferred to the actual type check that occurs on lines 64-67. The exceptions should arguably be the same - I

Dangers of renaming and removing runtime kinds

2019-09-16 Thread Sven Lange-Last
Hello Openwhisk community members, recently, PR #4390 [1] renamed runtime kind "java" to "java:8". While a change like this looks harmless at the first sight, it breaks all existing actions of this kind. This may not be important for developers and "occasional" usage of Openwhisk - but it