Hello fellow CFEngineers,
We are happy to announce the availability of CFEngine 3.27.0.
Patch a new LTS series, it's packed with great stuff.
To highlight just a few things:
classfilterdata()cfbs convert and cfbs analyzecf-agent and choosing to evaluate policy in the order it's written.For more details, please read our blog post.
Community packages for 3.27.0 are available from the community download page and public repositories. Enterprise packages are available from the Enterprise package download page.
| Description | Architecture | URL | SHA256 |
| Masterfiles ready-to-install tarball | no arch | https://cfengine-package-repos.s3.amazonaws.com/community_binaries/Community-3.27.0/misc/cfengine-masterfiles-3.27.0-1.pkg.tar.gz | 9c2fafebf8f0cb8ed70b4b3f3c445d0501de88abd7b7f0260083b4dd27724788 |
| Linux binary tarball (unsupported) | x86_64 | https://cfengine-package-repos.s3.amazonaws.com/community_binaries/Community-3.27.0/misc/cfengine-community-3.27.0-1.x86_64.pkg.tar.gz | d453e80b664efecb2c0261f3e2af058fb465de063889b3778353260cc9f3d202 |
| Masterfiles source tarball | no arch | https://cfengine-package-repos.s3.amazonaws.com/tarballs/cfengine-masterfiles-3.27.0.tar.gz | 84803035168af3e43c1fb25ba5f90561dec33b151ef5d5359a108a06c4c7c61d |
| Source code tarball | no arch | https://cfengine-package-repos.s3.amazonaws.com/tarballs/cfengine-community-3.27.0.tar.gz | d793e830b02e09843bf8ece1efd538cd65fa0428f249bbf7e371ca52d5f97b43 |
Hi Markus,
From what I understand is that you do not support platform versions that are not supported anymore by their vendors. So Debian 11 for instance is stated as being dropped from support in the blog post. Does this imply enterprise support or the community packages and masterfiles as well?
That's correct. We drop platforms after they have been dropped by their vendors and based on demand from our customers. This applies to Enterprise, Community and masterfiles.
What I'm really wondering is, will I not be able to use CFEngine 3.27 on a Debian 11 agent? From the looks of it debian_11 is present in the `standalone_self_upgrade.cf` policy for instance.
When support for a platform is dropped we don't proactively try to prevent those platforms from working but we do not try to maintain them. References to old platforms may live on for years or may be tidied up from time to time. But importantly, we don't build packages, we don't test them in CI.
If you would like for us to continue to maintain some old platform the best way is to reach out about extended support
Will you be able to use CFEngine 3.27 on Debian 11? We currently have no plans to build 3.27 or newer packages, but if you build them it's likely to work as you would expect.
We will continue to produce binaries for Debian 11 for 3.24.x until it is end of life.
Do you have any other questions about supported platforms?
Hi Markus
There are two potential drawbacks in the dual-version approach that you should be aware of (maybe you are already):
Ciao,
-- bronto