[RTFACT-7536] Allow slashes in Vagrant box names Created: 01/Jun/15  Updated: 08/Jul/19

Status: Open
Project: Artifactory Binary Repository
Component/s: Vagrant
Affects Version/s: 3.8.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Michael Kuzmin Assignee: Unassigned
Resolution: Unresolved Votes: 9
Labels: None


 Description   

Please allow box names in form of `org/name` with a slash in the value.

Private Vagrant boxes can also have organization prefixes, and moreover, these prefixes are mandatory for some Vagrant features:

1) You support `vagrant box add <url>` use case, but it is not the main way to download boxes. Preferred way to specify alternate Vagrant server is by `config.vm.box_server_url` parameter in Vagrantfile, or by `VAGRANT_SERVER_URL` environment variable.
But to use this feature Vagrant requires all box names to have organization prefixes.

2) `vagrant box list` command shows all the boxes in a flat list. It's important to distinct, where each of multiple `ubuntu` boxes come from. Organization prefixes solve this issue.



 Comments   
Comment by Michael Kuzmin [ 12/Jun/15 ]

Can we have an update please?

Comment by Ariel Seftel [ 23/Jun/15 ]

We will review this request on our next roadmap meeting and will update the Jira accordingly.

Comment by Ethan Spoelstra [ 05/Jan/16 ]

Has this been fixed in the pending release?

Comment by Michael Kuzmin [ 21/Jul/16 ]

After a year of waiting, I solved this problem by an external tool:
https://github.com/mkuzmin/vagrant-proxy

This is a tiny web service, which converts a list of box-files into a correct Vagrant format. As a side effect, it also works with open source edition of Artifactory.

Comment by JAmes Atwill [ 26/Oct/16 ]

Nice find. Just ran into this. I feel like until this is fixed it should at least be documented?

Comment by Ethan Spoelstra [ 11/Feb/18 ]

I believe some recent updates fix URL encoded slashes but I haven't set up a Vagrant repository in Artifactory in my last two positions and it will probably be a while before I do so again to test.

Comment by Tommy McNeely [ 27/Jun/18 ]

For what its worth, we have found that you an URLENCODE the slash (%2F), and it works (at least on our Artifactory 5.6.2). It is not an awesome solution, but a workaround.

curl https://artifactory.company.com/artifactory/api/vagrant/vagrant-local/company%2Fcentos-7.5

 

The API should be able to handle the slashes automatically, though.

 

Generated at Wed Feb 19 05:30:03 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.