Skip to content
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

claw-playbook: Move roles from internal to galaxy #764

Closed
whikloj opened this issue Dec 15, 2017 · 2 comments
Closed

claw-playbook: Move roles from internal to galaxy #764

whikloj opened this issue Dec 15, 2017 · 2 comments

Comments

@whikloj
Copy link
Member

whikloj commented Dec 15, 2017

This ticket is to complete the work necessary to have the internal roles (currently all except webserver-app) removed from claw-playbook and instead retrieved via ansible-galaxy.

@whikloj
Copy link
Member Author

whikloj commented Dec 15, 2017

switching to external roles, I'm now getting some interdependency problems with geerlingguy.drupal-console.

ERROR! the role 'geerlingguy.php' was not found in /sw/var/www/DAM2/claw-playbook/roles:/sw/var/www/DAM2/claw-playbook/roles/internal:/sw/var/www/DAM2/claw-playbook/roles/external:/sw/var/www/DAM2/claw-playbook/roles/external:/sw/var/www/DAM2/claw-playbook

The error appears to have been in '/sw/var/www/DAM2/claw-playbook/roles/external/drupal-console/meta/main.yml': line 3, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

dependencies:
  - geerlingguy.php
    ^ here

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I think we are going to need to drop all our use of the name: in requirements.yml and change our naming to use the full username.rolename.

Trying that next.

@whikloj
Copy link
Member Author

whikloj commented Dec 20, 2017

Also, downloading more than 20 roles in a row seems to make us hit the Github rate limiter. So the first time you download claw-playbook the process will be.

> vagrant up
<stuff happens>
...
ERROR! Unexpected Exception, this is probably a bug: Failed to connect to galaxy.ansible.com at port 443: [Errno 8] nodename nor servname provided, or not known
to see the full traceback, use -vvv
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
> vagrant provision

Then it continues along.

I have switched around the order etc and it always fails on the 21st external role.

Not a huge issue, but kind of a pain.

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

No branches or pull requests

1 participant