Richard Cox

@DaiYuzeng At the moment we are only merging critical defects, so i've marked this as `2.7.0`

This shouldn't be too bad too implement. Though need to consider - feature should be off by default and enabled by admin at deploy time - add endpoint button should...

Hi @cyrano007 , we track all our issues in github and tag those that come from outside the team with `Community`

From slack https://cloudfoundry.slack.com/archives/C80EP4Y57/p1610704654001800 ``` Now i’m at a point where i’m implementing the logic for differentiating between user-endpoints and admin-endpoints. Since n users can create m endpoints, i thought about...

1) We don't have any way via the api to retrieve Stratos user information other than that of the person signed in. You will need to add an additional `/user`...

3. If this makes it simpler, ok. If the admin see's all there would be nothing stopping them adding the same endpoint themselves. Just had a thought on this, are...

`Added a creator column to the cnsi table, which stores the id of the user who created the endpoint.` I think the db changes should not be gated on the...

`I think the db changes should not be gated on the config value.` Sorry, i meant the creation of the column in the db should not be gated. Think tracking...

I've managed to find the original explanation why the cnsi guid was made deterministic - https://github.com/cloudfoundry/stratos/pull/3031#issuecomment-423323347. With that in mind as long as your changes don't break their requirement you're...

I think going on the principal that admins are all seeing they should, though this may cause issues in the frontend when deciding to show extra endpoint information given the...