Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

Periods in role names cause installs to fail #9

Open
gregdek opened this issue Jul 31, 2015 · 6 comments
Open

Periods in role names cause installs to fail #9

gregdek opened this issue Jul 31, 2015 · 6 comments

Comments

@gregdek
Copy link
Contributor

gregdek commented Jul 31, 2015

[alex@dev ~]# ansible-galaxy install joshualund.ruby-2.0.0

downloading role '0', owned by joshualund.ruby-2.0
Sorry, joshualund.ruby-2.0.0 was not found on galaxy.ansible.com.

@gregdek gregdek added the bug label Jul 31, 2015
@gregdek
Copy link
Contributor Author

gregdek commented Aug 24, 2015

This is an issue with the way the Galaxy client deals with namespacing. Should be fixable by changing the way we do matching on the client side -- but we'll see. ;)

@gregdek gregdek added this to the 1.1 milestone Aug 24, 2015
@chouseknecht
Copy link
Contributor

It appears that extra periods were already considered. Here is my experience:

Forked role jlund/ansible-ruby-2.1.
Imported chouseknecht/ansible-ruby-2.1. Did not supply an optional name.
Imports as ansible-ruby-2_1 <-- notice . replaced by _

Install command is reported correctly inside galaxy as:

ansible-galaxy install chouseknecht.ruby-2_1

@chouseknecht
Copy link
Contributor

Is this something we should mention on the 'About' page? And... maybe for next release we should bring Sam in and turn our 'About' page into a mini doc site or something.

@gregdek gregdek modified the milestones: 1.1, 1.1.1 Oct 22, 2015
@gregdek gregdek added this to the 1.1.1 milestone Oct 22, 2015
@gregdek
Copy link
Contributor Author

gregdek commented Oct 22, 2015

We need to document the behavior somewhere.

@chouseknecht
Copy link
Contributor

Updated the Add A Role page:

addrolepage

Updated the About page:

intropage

@jlmitch5
Copy link

verified docs change is present. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants