Closed djdanielsson closed 2 months ago
After doing all this I had a thought... I wonder if I should be doing lineinfile and replacing hostnames and passwords, along with moving the playbook to the root that would then keep one set of config files to manage instead of two or another idea would be to create links
@djdanielsson @jpmens Hi, thanks for huge contribution! Frankly, I am suprising at this big collection to be sent through PR.
I think it would be better to continue development of this collection in your separate, independent repository🤔 Since my repository is something I maintain in my spare time between my day job, it might be a bit hard for me to keep both guides and collection to work and to be updated without any inconsistence with the guide at the same time.
I have no objection to publishing the collection in your namespace with you as the author. I don't know if I will develop my own collection in the future, but I can consider, for example, adding link to your repository or collection as the one of the "Related Projects" in my README,md
.
I might do that, though to be honest I already help maintain around 4 collections already so I definitely understand trying to be careful to not add a lot more. I will rewrite it a bit and see if I can make it work directly with the current config files and locations easily that should make it a lot less effort to maintain. If you think it is still too much after that then I will consider publishing it myself.
then I will consider publishing it myself.
I would appreciate it if you could do so. I will probably have less spare time than I do now starting in May due to family matters, at the end of my paternity leave. As a solution for #334 I have intended to be a small playbook that deployes only AWX, so to be honest a large collection including EDA and Galaxy NG would be a bit much for me to keep it to be maintained and updated. Thanks for your understanding😢
this is the first run through to automate the tasks to deploy awx, galaxy_ng, and eda to work towards #334