As more and more production system uses openwhisk,
It seems we need some feature to protect their service safe from mistake.
for example, when users create action use like below(add annotation "lock":true)
curl -X PUT -H "Content-type: application/json" --user
23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP
-d
'{"namespace":"guest","name":"hello","annotations":[{"key":"lock","value":true}],"exec":{"kind":"nodejs:default","code":"//
Licensed to the Apache Software Foundation (ASF) under one or more
contributor\r\n// license agreements; and to You under the Apache License,
Version 2.0.\r\n\r\n/**\r\n * Hello, world.\r\n */\r\nfunction main() {\r\n
return {\"payload\":\"Hello world\"};\r\n}\r\n"}}'
'http://xxx.xxx.xxx.xxx:port/api/v1/namespaces/guest/actions/hello?'
The lock field will be added in couchdb's annotation, like below
"annotations": [ { "key": "exec", "value": "nodejs:6" }, { "key": "lock",
"value": true }
So this action can't be deleted/updated until the protection is updated to false
This is the patch: https://github.com/apache/incubator-openwhisk/pull/4058
If this patch is merged into upstream, the wsk side will do some changes, add
unlock feature to wsk to enable update or delete operation, for example
wsk action update hello --unlock
So we can discuss there, is it necessary to add this feature? or any other
suggestions.
