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
Context: In our company we have private registry, and self-hosted registrator, and we use ssh keys for authentication for our self-hosted github.
Problem: I can not register new version of package when Registry is already using ssh address using the web UI.
In our registry, for packages we have e.g. Package.toml in the registry
name = "InternalPackage"uuid = "a2c437b0-bf6b-41a1-8a62-162a814afa99"repo = "git@git.our_company.com:our_org/InternalPackage.jl.git"
To return SSH URI, there would need to be r.ssh_url instead of r.clone_url (and analogously r.ssh_url_to_repo instead of r.http_url_to_repo for GitLab).
I guess the most straightforward way to make it work is to pass additional parameter which marks if HTTPS or SSH was used and delegate it to cloneurl method and there return proper URI.
Context: In our company we have private registry, and self-hosted registrator, and we use ssh keys for authentication for our self-hosted github.
Problem: I can not register new version of package when Registry is already using ssh address using the web UI.
In our registry, for packages we have e.g.
Package.toml
in the registrywhen I put
git@git.our_company.com:our_org/InternalPackage.jl.git
to the form https://github.com/JuliaRegistries/Registrator.jl/blob/master/src/webui/templates/select.tplI obtain: ERROR: Package URL is invalid.
when I put
https://git.our_company.com:our_org/InternalPackage
to the form https://github.com/JuliaRegistries/Registrator.jl/blob/master/src/webui/templates/select.tplI obtain: ERROR: Registration failed: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.
Since we don't have anonymous clone allowed, we are using SSH keys everywhere and thus having https address would complicate things for us a lot.
The text was updated successfully, but these errors were encountered: