This PR introduces a new role 'pre-checks', to our Ansible playbook for the PostgreSQL cluster project. The purpose of this role is to consolidate various preliminary checks scattered throughout the code into one cohesive role. This new role is designed to run before any cluster deployment begins.
Why this Change is Necessary:
The creation of the pre-checks role aims to improve the overall readability, maintainability, and failure handling of our playbook. By centralizing all preliminary checks, we can prevent scenarios where the playbook halts in the middle due to a failed check for a specific role. Instead, all checks are performed upfront, ensuring that actual deployment will only proceed if all checks pass.
Key Points:
The pre-checks role will be the first role executed during the playbook run. All existing preliminary checks from other roles will be migrated into this role. Future checks can be easily added to this role, simplifying the process for further updates or additions.
Expected Outcome:
With these changes, we anticipate smoother playbook executions with fewer disruptions. This should enhance the user experience by providing clear, upfront information about any issues that may affect the deployment of the cluster.
Summary of Changes:
This PR introduces a new role '
pre-checks', to our Ansible playbook for the PostgreSQL cluster project. The purpose of this role is to consolidate various preliminary checks scattered throughout the code into one cohesive role. This new role is designed to run before any cluster deployment begins.Why this Change is Necessary:
The creation of the pre-checks role aims to improve the overall readability, maintainability, and failure handling of our playbook. By centralizing all preliminary checks, we can prevent scenarios where the playbook halts in the middle due to a failed check for a specific role. Instead, all checks are performed upfront, ensuring that actual deployment will only proceed if all checks pass.
Key Points:
The pre-checks role will be the first role executed during the playbook run. All existing preliminary checks from other roles will be migrated into this role. Future checks can be easily added to this role, simplifying the process for further updates or additions.
Expected Outcome:
With these changes, we anticipate smoother playbook executions with fewer disruptions. This should enhance the user experience by providing clear, upfront information about any issues that may affect the deployment of the cluster.