ok-borg / api Goto Github PK

For now access control to public snippet is made using a flobal map directly in the go code. Thismake the api nor stateless. We neesto move this functionality to mysql.

This is composed of the following task:

• improve current http api to specify the private things in the request body
• save organizations informations in elastic search associated to the snippets

Currently access control apply to any kind of update/create snippet. This means that the user is limited to something like 50 edit or create snipper per day, and this restriction apply to public/owned/organization snippets.
We may need to change this behavior, and apply restrictions only on public snippets.
@anas10, @crufter any thought ?

This endpoint will allow us to collect usage informations about our api. Nothingto track ou user. But at leastwe want to know the how many people areuainf each version of the api in order to calculate the impact of possible changes or deprecation for a specific version

The web app may need in the future some kind of auto-completion on snippets titles.
We need to decide if auto completion must apply on Public / user only / organization snippet, by specifying explicitly one, or on all the content accessible by the user.