Details
-
Improvement
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
1
Description
Eventing started supporting full RBAC with scoped eventing functions in Neo and same function name can appear under different function scopes. With this all the life cycle operation needs to include "bucket" and "scope" name in uri(by default its value is * for backward compatibility)
Rest api:
/api/v1/functions/<function name>/<lifecycle operation>?bucket=<function_scope.bucket>&scope=<function_scope.scope>
Example:
/api/v1/functions/test/deploy?bucket=b1&scope=s1
Example schema: https://github.com/couchbase/eventing/blob/master/parser/handler_schema.json
status and stats api will include "function_scope" value to differentiate between different function
curl -X GET -u Administrator:password http://localhost:9300/api/v1/status{ "apps": [ { "composite_status": "undeployed", "name": "test", "function_scope": { "bucket": "src_bucket", "scope": "_default" }, "num_bootstrapping_nodes": 0, "num_deployed_nodes": 0, "deployment_status": false, "processing_status": false, "redeploy_required": false } ], "num_eventing_nodes": 1}%
|
Attachments
Issue Links
- relates to
-
MB-51480 SDKs should uptake Eventing status API additions due to RBAC
- Closed
-
PYCBC-1277 Eventing function management fails when using 7.1
- Resolved