Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add role 'pre-cheks' #369

Merged
merged 12 commits into from
Jun 9, 2023
Merged

Add role 'pre-cheks' #369

merged 12 commits into from
Jun 9, 2023

Conversation

vitabaks
Copy link
Owner

@vitabaks vitabaks commented Jun 9, 2023

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.

Summary of Changes:

This commit 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.
@vitabaks vitabaks self-assigned this Jun 9, 2023
@vitabaks vitabaks added the enhancement New feature or request label Jun 9, 2023
@vitabaks vitabaks merged commit 7c1237a into master Jun 9, 2023
19 checks passed
@vitabaks vitabaks deleted the pre-checks branch June 13, 2023 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant