My son would like you all to know that watching @ansible playbooks run with cowsay is amazing and awesome, and is akin to cows simon says with servers.
He also told me, repeatedly, to tell you all this.
Is the #Ansible I knew and loved fading slowly into the void?
I had high hopes and optimism after the big collections push last year, but business interests are slowly kneecapping the OSS/community side, partly intentionally, and partly through disinterest.
Update for Ansible release schedule and versioning info:
- ansible package will move to semver (MAJOR.MINOR.PATCH)
- The next major ansible release will be 3.0.0, no ansible 2.11 release
More details + the proposed release dates: https://t.co/rmPXqJToO6
#ansible#community
Ever wanted to write a new @ansible module for @ForemanProject but didn't know where to start? There is an article describing exactly this now!
https://t.co/x08VnvbI9F
Btw, if you'd like to contribute/suggest #Ansible content for The Bullhorn, you can comment with your proposal on github: https://t.co/O2GnDtOPdW
Hope to see more #community contributed content!
A boiler plate example to an @ansible inventory plugin, including how to use Ansible's caching facilities.
It shows the use case of retrieving data from a remote API, which might be a
slow or costly action, you may want to cache.
https://t.co/byjnYgyHBc
95% of the so called "problems" in YAML exist because you assume strings are just strings, and you don't quote them.
Always quote values, unless you know how they will be parsed.
Did you know? @ansible did NOT deprecate with_* loops (e.g. with_items?) . https://t.co/oEqjsA6fh5
>We have not deprecated the use of with_<lookup> - that syntax will still be valid for the foreseeable future.