Are you saying you have to issue a "god" level API access token to access a single docker (private) image in the Digital Ocean container registry?
There is basically no granularity.
{"auths":{"registry.digitalocean.com":{"auth":"<base64-encoded-credentials>"}}}
If you decode the base64 encoded credentials it will be a string like "<token>:<token>" with either a read only or read/write token to all of the resources on DO.think my reply shortness maybe has you misunderstanding me?
The fact that an API token can only have read/write project wide basically results in everything you said.
No RBAC on services. No RBAC on specific API actions. Anyone with read+write can do/nuke everything.
That’s why I’m migrating $COMPANY off to AWS as fast as I humanly can by myself.
> you can simulate what `doctl registry login` does by using an API token string as the username and password when calling `docker login`
https://docs.digitalocean.com/products/container-registry/ho...