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
The registry_token variable (action.yml#L20) is required for this action to run.
I am unsure as to where the environment variable GH_TOKEN is actually used and how it is authenticating. But its an issue if you want to use other image registries than ghcr.oi and need to use docker-credential-helpers, eg. for authenticating to Google Artifact Registry.
My proposal is to make registry_token optional and still make the bluebuild build command push the image but not authenticate if the registry_token is not set.
That way you could add a docker-credential-helper and docker login step before the blue-build action which would enable the use of other registries.
The text was updated successfully, but these errors were encountered:
Kerwood
changed the title
Make registry_token variable optional
feat: make registry_token variable optional
May 28, 2024
The
registry_token
variable (action.yml#L20) is required for this action to run.I am unsure as to where the environment variable
GH_TOKEN
is actually used and how it is authenticating. But its an issue if you want to use other image registries than ghcr.oi and need to use docker-credential-helpers, eg. for authenticating to Google Artifact Registry.My proposal is to make
registry_token
optional and still make thebluebuild build
command push the image but not authenticate if theregistry_token
is not set.That way you could add a
docker-credential-helper
anddocker login
step before theblue-build
action which would enable the use of other registries.The text was updated successfully, but these errors were encountered: