After a discussion with @bernd, we decided this role is trying to do too much. It should not be installing MongoDB or Java itself. That should be pulled in from another role. If roles for these tools are defined explicitly in the playbook, then users can pick whatever role they want to install these tools, rather than the one we choose.
By focusing on just installing Graylog, we can make the role a lot more stable.
I'll update the docs with good examples on how to include these roles before running our role. I'll also fix up the Molecule tests to pull in these dependencies explicitly, rather than through meta/main.yml
This is in no way backwards compatible, but I think it'll be better.
After a discussion with @bernd, we decided this role is trying to do too much. It should not be installing MongoDB or Java itself. That should be pulled in from another role. If roles for these tools are defined explicitly in the playbook, then users can pick whatever role they want to install these tools, rather than the one we choose.
By focusing on just installing Graylog, we can make the role a lot more stable.
I'll update the docs with good examples on how to include these roles before running our role. I'll also fix up the Molecule tests to pull in these dependencies explicitly, rather than through
meta/main.yml
This is in no way backwards compatible, but I think it'll be better.