community.postgresql VS Ansible

The community.postgresql collection released a new version: 3.2.0.

We are happy to announce that the community.mysql collection has found a new maintainer: Felix Hamme (betanummeric on GitHub/Matrix)! He's also already a maintainer of the community.postgresql collection and has a great history of contributions in both. Thanks, Felix, and welcome to the crew!:)

The community.postgresql collection has released two new version: 1.7.9 and 2.4.1. They revert the breaking change accidentally introduced in the previous version (which was intended for a later major release).

The community.postgresql collection version 2.3.1 has been released (changelog). Thanks to vonschultz and hunleyd!

The community.postgresql team has released 1.7.6 as a bugfix release.

We are also happy to announce a new maintainer of the community.postgresql collection - Felix Hamme (betanummeric on GitHub)! Our congratulations, Felix, and thank you for your great contribution in many collections and desire to help!

The community.postgresql maintainers need your feedback! A proposal for formalizing the supported PG versions has been filed here and needs your input. If adopted, the collection will issue major releases yearly and each major release will officially support the five major version of PG supported at that time. We think this will ultimately improve the collection and improve the end user's experience but we need your input. We look forward to hearing from everyone!

Recently, we opened https://github.com/ansible-collections/community.postgresql/issues/276 to discuss formalizing the supported PostgreSQL versions in the community.postgresql collection. This is a big change for the collection and we want to ensure the proposal makes sense for the collection's users. If you use the collection, please review the proposal and add your thumbs up/down, comment, etc. Thanks!

The community.postgresql collection has released 1.7.3 and 2.1.4 to fully deprecate Ansible 2.9/2.10. Thanks to our newest contributor jchancojr and everyone else involved!

Ansible is an open-source IT automation tool that simplifies application deployment, cloud provisioning, and configuration management across diverse environments. It uses a declarative language to describe the desired state of the system, and then takes the necessary actions to achieve that state. Ansible has become incredibly popular due to its simplicity, agentless architecture, and extensive community support. Document: ansible.com, ansible basics

Ansible v2.16

Ansible is a tool used to help manage software automation processes, configuration management across machines, deployment as well as remote execution of commands and scripts. In sports, Ansible operates as the coach of your team by providing strategies (playbooks), and actions, and ensuring the smooth execution of tasks across your infrastructure, just like a coach guides and directs players (Servers)during a game.

They support for-if from python, too: https://jinja.palletsprojects.com/en/3.1.x/templates/#loop-f... but I haven't tried the "recursive" keyword to know if ansible supports that. I say "ansible supports that" because they don't just drop jinja2 into ansible and call it a draw, they have a bunch of custom execution integrations: https://github.com/ansible/ansible/blob/v2.16.3/lib/ansible/...

To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck

In this article's context, it is simply a tool that provides a declarative way to automate your machine/OS to configure the development machine as you want (install package, modify the configuration, etc). Examples of these tools are Ansible, Puppet, etc.

Now we're getting more tangential, but for years, Ansible releases were named for Van Halen songs (see old Changelog here: https://github.com/ansible/ansible/blob/v1.8.4/CHANGELOG.md)

In the lab to follow, we'll quickly provision a 3-node kubeadm cluster (1 master, 2 workers) on the cloud provider of your choice using an automation stack comprised of OpenTofu and Ansible, then deploy Rook Ceph using the official Helm charts and confirm that we are now able to successfully create CSI volume snapshots from PVCs by reusing the MinIO example from our last article.