click, click, poof! ansible-navigator 2.0.0 "The refinement release" is available upstream. Thank you @ganesh634 @relrod6 @sbarnea@webknjaz@thedoubl3J Alison and Priyam @ansible for everything you did to make it possible. https://t.co/7QKlrYsI0A
@willmcgugan If you are suggesting a welcoming place where both experienced and less experienced developers can participate in these projects and everyone learns from each other and the bits benefit.... Why not? Disclaimer, I'm still new at all of this.
Our son Winston recently turned 2 and ansible-navigator just had a 2.0.0rc1 release. It is hard to explain how much joy both bring me. @ansible https://t.co/8YekOQJscd They are strangely connected.
@geerlingguy Thank you. Had you done this in the first place, it would have saved us both a lot of frustration. Your participation and contributions are, and always will be appreciated.
@geerlingguy So maybe next time, add a disclaimer explaining that you may have been too busy to see the change in a project that you are invested in, rather than tweeting without context or history provided. Everything is done in the open for a good reason, participate or accept.
@geerlingguy You can't have it both ways. Following HEAD suggests you are interested in incremental changes to the project and desire to be a participant, but I don't see you provided any feedback on the PR that enabled the rule as default: https://t.co/hSYL83YCkE
@geerlingguy I should also mention. ansible-lint follows semver for versioning, this was a major release (6.x) for ansible-lint and was noted in the release notes. https://t.co/BplVgFJuYi
@geerlingguy The rule can be disabled, and the use of ansible-lint is optional. I'm not sure where the "enforcement" is happening. ansible-lint recommends practices for production grade content and will continue to do so.
Still using ansible-playbook?! Check out another reason to switch to ansible-navigator for inspection of your local environment and super fast automation content authoring straight from examples in documentation. All without leaving your editor. https://t.co/9HCUDNdqHS
The next generation of Red Hat Ansible Automation Platform is here. Join us on November 4th to hear directly from the product team about key changes and new features, followed by a live Q+A session. https://t.co/5gx7cX9lSg
@akira6592 Sorry about that, it seems changelog generation didn't happen. The release is mostly bug fixes, the only new functionality is `container-options`, allows for additional params to be passed directly to the container engine command.
@DonPwrShellHunt@ansible That probably should read, ansible-playbook cannot run containers, navigator runs the container in the very much the same fashion as controller would, it's a pre-production validation tool among other things to vet the EE