Ansible 4.0
groups.google.com
Ansible 4.0
1–10 of 141 posts
Re: Ansible 4.0
#2It was harder than I expected to find the changelog so I’ll leave the link
https://github.com/ansible-community/ansible-build-data/blob...
Re: Ansible 4.0
#3It was harder than I expected to find the changelog so I’ll leave the link https://github.com/ansible-community/ansible-build-data/blob...
checked the release notes and it seems like they still don't allow you to run ansible with "python -m". that would have fixed a few issues with virtual environments.
Re: Ansible 4.0
#4I always cringe when I read the word 'final'. :)
Too many years in the industry with projects called final... Basically a tag saying 'this shit ain't never gonna be over! Run for the hills!'.
And nothing is more set in stone than a bunch of yml ;) /s
Re: Ansible 4.0
#5I always cringe when I read the word 'final'. :) Too many years in the industry with projects called final... Basically a tag saying 'this shit ain't never gonna be over! Run for the hills!'. And nothing is more set in stone than a bunch of yml ;) /s
Final as in it's the actual release and not a candidate, not that it's the final version of Ansible jfyi
Re: Ansible 4.0
#6I always cringe when I read the word 'final'. :) Too many years in the industry with projects called final... Basically a tag saying 'this shit ain't never gonna be over! Run for the hills!'. And nothing is more set in stone than a bunch of yml ;) /s
Final as in it's the actual release and not a candidate, not that it's the final version of Ansible jfyi
We have a word that describes that better than 'final': release. And if it's on physical media, you could even call it GM (Golden Master). They are not words that stand on their own, you would combine it with the artifact name and the version you are releasing.
Release of the following:
Name: ansible
Version: 4.0.0
Combined, it's the "Ansible 4.0.0 Release" in whatever order makes sense. If you have something that is not a release, then you would not call it a release. But if you think you are close to a release and you want to be sure, you could state that this is a candidate but not entirely sure. You can even have multiple incarnations of candidates. You end up with a "release candidate" and you could suffix it with number if you have more than one.
While many creators and vendors some up with all sorts of schemes, there are a few standards available with extensive documentation like https://semver.org or simply mimic what well-respected projects are using.
The problem is of course that nobody agrees on anything if you have a large quantity of things (including large quantity of people), and the urge to create 'a standard to fix the mess' which just adds to the mess in the end. This whole thing is of course not all that important in the grand scheme of things, and an intersection of the 'standards' XKCD commic and 'everything is great and nobody is happy' seems to be where we end up every time.
Re: Ansible 4.0
#7Pretty cool but Ansible just seems too slow to me. I'm just comparing this against like native scripting, Terraform, etc. I guess Ansible is still the best option for configuration management, but I keep hoping someone will come out with a new tool, preferably built with Go or Rust.
Re: Ansible 4.0
#8I always cringe when I read the word 'final'. :) Too many years in the industry with projects called final... Basically a tag saying 'this shit ain't never gonna be over! Run for the hills!'. And nothing is more set in stone than a bunch of yml ;) /s
You keep using the word final. I don't think it means what you think it means...
Here it doesn't mean "the project is done, no more development".
It just means this is the official release of version 4.0 - e.g. no more betas, etc.
Re: Ansible 4.0
#9Pretty cool but Ansible just seems too slow to me. I'm just comparing this against like native scripting, Terraform, etc. I guess Ansible is still the best option for configuration management, but I keep hoping someone will come out with a new tool, preferably built with Go or Rust.
I doubt building ansible in go or rust we save more than a few ms in the average playbook run.
Re: Ansible 4.0
#10Earlier quoted context omitted.
Final as in it's the actual release and not a candidate, not that it's the final version of Ansible jfyi
We have a word that describes that better than 'final': release. And if it's on physical media, you could even call it GM (Golden Master). They are not words that stand on their own, you would combine it with the artifact name and the version you are releasing. Release of the following: Name: ansible Version: 4.0.0 Combined, it's the "Ansible 4.0.0 Release" in whatever order makes sense. If you have something that is…
>We have a word that describes that better than 'final': release.
The release would still be 4 even when it's in beta or alpha stage, so no.