-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roles don't connect to one another #46
Comments
That's interesting. I would have expected postgresql to be a dependency of gitlab. You do have all of your dependencies wired up with Ansible right? |
jimbocoder
added a commit
to insurancezebra/ansigenome
that referenced
this issue
May 25, 2016
Rather than have a bunch of rules about valid role names, the dot format allows quoting identifiers, so this is much easier and should fix related issues including nickjj#46
adrien-mogenet
pushed a commit
to ContentSquare/ansigenome
that referenced
this issue
Aug 10, 2016
Rather than have a bunch of rules about valid role names, the dot format allows quoting identifiers, so this is much easier and should fix related issues including nickjj#46
AlbanAndrieu
pushed a commit
to AlbanAndrieu/ansigenome
that referenced
this issue
Sep 2, 2016
Rather than have a bunch of rules about valid role names, the dot format allows quoting identifiers, so this is much easier and should fix related issues including nickjj#46
The issue still persists in ansigenome ade5c2b |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
The picture will likely speak for itself:
The roles are not connected to one another and instead of having a graph where everything starts from the
comb/
role and then connects to one another,ansigenome
seems to miss that the roles should indeed all be connected.Could you point me into the direction to fix it, please?
The text was updated successfully, but these errors were encountered: