Details
-
Improvement
-
Resolution: Fixed
-
Major
-
7.1.1
-
None
-
1
Description
We normally do not publish the setting to turn off the recursion check, rather informing customers that run into this issue of the REST endpoint.
We have customers that are moving to 7.x and moving their default scope and collection into custom scopes and collections, and are using the same bucket for SRC and DEST. This triggers a warning and prevents the function from deploying.
Using the same bucket is allowed if the functions have been examined to not raise the risk of recursion, via the use of the rest endpoint:
curl -X POST -u $CB_USERNAME:$CB_PASSWORD http://localhost:8091/_p/event/api/v1/config -d '\{"allow_interbucket_recursion":true}' |
and then turn it off when they are done
curl -X POST -u $CB_USERNAME:$CB_PASSWORD http://localhost:8091/_p/event/api/v1/config -d '\{"allow_interbucket_recursion":false}' |
This should be documented especially since in serverless environments we will give a customer only one bucket.
https://docs.couchbase.com/server/current/eventing/eventing-api.html
|