SDKs should uptake Eventing status API additions due to RBAC

Recent SDK testing shows a change in the Eventing Status API. Specifically the response from retrieving the status (/api/v1/status) has changed.

Was this something previously communicated between the teams? From the SDK perspective (and possibly other consumers of the API) the change could be breaking. Admittedly, I do not know if there was previous communication about the change or if there is supposed to be an understanding on the state of the API, so I cannot say anything definitive. I am just working off of the SDK RFC.

I do not know which build version of 7.1 the change occurred, but it does seem to be somewhat recent.

Previous response:
What we have for the SDK RFC

{

 "apps": [

  {

   "composite_status": "deployed",

   "name": "aaa",

   "num_bootstrapping_nodes": 0,

   "num_deployed_nodes": 1,

   "deployment_status": true,

   "processing_status": true

  }

 ],

 "num_eventing_nodes": 1

}

Latest response:
the function_scope field was added.

{

 "apps": [

  {

   "composite_status": "deployed",

   "name": "aaa",

   "num_bootstrapping_nodes": 0,

   "num_deployed_nodes": 1,

   "deployment_status": true,

   "processing_status": true,

   "function_scope": {"bucket": "*", "scope": "*"}

  }

 ],

 "num_eventing_nodes": 1

}