Juan Carlos Mejías Rodríguez
Juan Carlos Mejías Rodríguez
@kaotika please check out [2.0.0-alpha.3 release](https://github.com/greenled/portainer-stack-utils/releases/tag/v2.0.0-alpha.3). It includes a first aproximation to proxying requests from a Docker client to Portainer, which should fulfill your config and secret management needs.
@kaotika I found the root cause of the error. When a config/secret or any other Docker resource is created with the proxy method no resource control policy is added for...
@deviantony please could you give some clarification here. I see Portainer injects a `Portainer` field with access control information in the JSON responses for inspecting Docker resources. This is widely...
Thank you for the info @deviantony. The example you provide works for resources *created with the stack*. The idea of managing resource control came from the need of using external...
BTW @kaotika, the number in the log after `FATA` represents how many seconds have passed since program started.
@kaotika on a second thought, design could be an even simpler (I think) mix of both aproaches. As removing an access control is the same as setting it to public,...
This isue is being worked on in the `several-changes` branch. Should be closed once that branch is merged.
I imported the project into GitLab, but only the repository was imported: no issues, no PRs....
/cc @tortuetorche
 It actually failed importing