We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The documentation for the installer uses JasonGiedymin.mesos so shouldn't the playbook installer use the same name as the role?
Not a big issue but just a small annoyance when testing this. :)
The text was updated successfully, but these errors were encountered:
true! @ernestas-poskus can you update before 0.6.0 release ?
ps: for some time we/you did not (request) update mesos_playbook_version like before: #56 (comment) Not sure how useful it is but I'ld either opt:
mesos_playbook_version
Sorry, something went wrong.
mesos_playbook_version will remove it, anyway we don't use it as compatibility tool.
We had plans to re-import role under/as AnsibleShipyard/ansible-mesos but I am not sure when this happens.
No branches or pull requests
The documentation for the installer uses JasonGiedymin.mesos so shouldn't the playbook installer use the same name as the role?
Not a big issue but just a small annoyance when testing this. :)
The text was updated successfully, but these errors were encountered: