Force use of UUID in clone URLs

Dear Support,

Is there a way to have only 2 clone URLs in the dropdown list:

  • the HTTP with the UUID
  • the SSH
    So not the have the ‘default’ HTTP that uses the repository name.

On top of this, is there a way to make the UUID based clone URL have the following syntax:
{scheme}://{user}@kvmech.kverneland.com/rhodecode/_{repoid}-{repo_basename}

where {repo_basename} is the directory name of the repo.

What I have tried, so far
1)
{scheme}://{user}@kvmech.kverneland.com/rhodecode/_{repoid}-{repo}
Working, but a mess:
{repo} unfortunately contains the repository group name as well, so the HTTP clone url is:
http://user@server/_uuid-repo-group/reponame
This is working, but ugly because of the in between repogroup name
The HTTP_UUID clone url is:
http://user@server/_uuid-repo-group/_uuid-uuid

2)
We have created a custom field for this purpose (repo_shortname), which is manually (automatic script) been filled up on every repository.

However this custom field cannot be used in the “Clone URL templates” settings. It is just not translated into its value, but remains {repo_shortname}
HTTP clone URL:
http://user@server/_uuid-{repo_shortname}
HTTP_UUID clone URL:
http://user@server/repogroup/reponame-{repo_shortname}
Even messier.

So to summarize:
I want the possibility to have 2 clone URLs: an http and an ssh based
I want the http based UTR have the following scheme: http://user@server/_uuid-reponame
where reponame is the name of the repository, without the repository group.

Regards,
Tamas

Hi,

Sorry this isn’t supported.

Too bad…

Where can I file a Feature Request?