WUD 8.0.0 - Registries issues in documentation: GITLAB / FORGEJO

[alexdelprete]

Regarding GITLAB, in docs I read this:

Previously I used only the token entry, and it worked, as per example shown above.
In latest WUD, in order to make it work, I had to add all 3 entries, and I also added the {REGISTRY_NAME} (I used PUBLIC), which is not present in documentation:

      - WUD_REGISTRY_GITLAB_PUBLIC_URL=https://registry.gitlab.com
      - WUD_REGISTRY_GITLAB_PUBLIC_AUTHURL=https://gitlab.com
      - WUD_REGISTRY_GITLAB_PUBLIC_TOKEN=zzzzzhghdhdshwsjdkwkiow

Regarding FORGEJO, docs say:

But it wouldn't work. I then tried to use a personal token to access the API, and it worked. So docs should be amended with WUD_REGISTRY_FORGEJO_{REGISTRY_NAME}TOKEN vs WUD_REGISTRY_FORGEJO{REGISTRY_NAME}_PASSWORD.

Thanks for the great release.

[fmartinou]

Hi,

---

Regarding Gitlab, I fixed the doc 👍

Env var	Required	Description	Supported values	Default value when missing
WUD_REGISTRY_GITLAB_{REGISTRY_NAME}_AUTHURL	🔴	Gitlab Authentication base url		https://gitlab.com
WUD_REGISTRY_GITLAB_{REGISTRY_NAME}_TOKEN	🔴	Gitlab Personal Access Token
WUD_REGISTRY_GITLAB_{REGISTRY_NAME}_URL	🔴	Gitlab Registry base url		https://registry.gitlab.com

---

Regarding Forgejo, the configuration is inherited from the Gitea configuration and for both the supported implemented conf is

        return this.joi.object().keys({
            url: this.joi.string().uri().required(),
            login: this.joi.alternatives().conditional('password', {
                not: undefined,
                then: this.joi.string().required(),
                otherwise: this.joi.any().forbidden(),
            }),
            password: this.joi.alternatives().conditional('login', {
                not: undefined,
                then: this.joi.string().required(),
                otherwise: this.joi.any().forbidden(),
            }),
            auth: this.joi.alternatives().conditional('login', {
                not: undefined,
                then: this.joi.any().forbidden(),
                otherwise: this.joi
                    .alternatives()
                    .try(
                        this.joi.string().base64(),
                        this.joi.string().valid(''),
                    ),
            }),
        });

So WUD_REGISTRY_FORGEJO_{REGISTRY_NAME}_TOKEN is currently not implemented 🤔 .

Can you, please, paste an example of the conf which is working for you?

[alexdelprete]

So WUD_REGISTRY_FORGEJO_{REGISTRY_NAME}_TOKEN is currently not implemented 🤔 .

Can you, please, paste an example of the conf which is working for you?

Basically, the account password doesn't work, I had to put the token in the password field:

      - WUD_REGISTRY_FORGEJO_CODEBERG_URL=https://codeberg.org
      - WUD_REGISTRY_FORGEJO_CODEBERG_LOGIN=myaccount
      - WUD_REGISTRY_FORGEJO_CODEBERG_PASSWORD=ykjewofnhwjefnMYTOKENwigfwnogjfwngwgn

Since this works, I guess it's better to rename the WUD_REGISTRY_FORGEJO_CODEBERG_PASSWORD variable WUD_REGISTRY_FORGEJO_CODEBERG_TOKEN.

I didn't read the Forgejo API docs, are you sure the API works with user/pw and not with user/token? For me it worked when using the PAT and not the password.