You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For CI systems that support configuring registry authentication via username and password, use a DigitalOcean API token as both the username and the password. The API token must have read/write privileges to push to your registry.
The username config option should allow a secret reference, the same way as password does. This doesn't work:
# Credentials for your image host.registry:
# Specify the registry server, if you're not using Docker Hubserver: registry.digitalocean.comusername:
- SECRET_REGISTRY_TOKENpassword:
- SECRET_REGISTRY_TOKEN
The text was updated successfully, but these errors were encountered:
kjellberg
changed the title
Allow registry.username to be a secret
Allow registry username to be a secret
Mar 5, 2023
# Credentials for your image host.registry:
# Specify the registry server, if you're not using Docker Hubserver: registry.digitalocean.comusername: <%= ENV.fetch("SECRET_REGISTRY_TOKEN") %>password: <%= ENV.fetch("SECRET_REGISTRY_TOKEN") %>
# Credentials for your image host.registry:
# Specify the registry server, if you're not using Docker Hubserver: registry.digitalocean.comusername: <%= ENV.fetch("SECRET_REGISTRY_TOKEN") %>password: <%= ENV.fetch("SECRET_REGISTRY_TOKEN") %>
Thanks, it works! But I still think it's a good idea to accept the array format for references on both properties.
ERB looks weird and ugly for non-ruby programmers and may actually scare them away :D
From DigitalOcean docs:
The username config option should allow a secret reference, the same way as password does. This doesn't work:
The text was updated successfully, but these errors were encountered: