Updating the Shebang and Implementing Security Settings

[rmottanet]

This pull request aims to improve the robustness, security, and portability of all project scripts by applying two essential best practices in shell scripting: optimizing the shebang and enabling security flags with the set command.

Implemented Changes:

The following modifications have been added to the beginning of all existing scripts:

1. Shebang Update:

• From: #!/bin/bash
• To: #!/usr/bin/env bash

This change significantly improves the portability of the scripts, ensuring that the Bash interpreter is correctly located in environments with different file system structures, instead of relying on a fixed path (/bin/bash).

2. Implementation of Security Settings:

• Insertion of the line: set -euo pipefail

This line activates three crucial flags for more secure and predictable code:

• -e (errexit): Forces the script to stop immediately if any command fails (exits with a non-zero code), preventing the execution of subsequent commands that depend on a previous successful state.
• -u (nounset): Causes the script to stop immediately when attempting to expand an undefined variable, which is a powerful defense mechanism against variable typos that could lead to destructive commands.
• -o pipefail: Ensures that a pipeline (command1 | command2) fails if any command within the pipeline fails, not just the last one.

Motivation:

This standardization aims to raise the quality and reliability of our code, aligning it with modern shell scripting development standards. * Robustness and Debugging: By enabling -e and pipefail, errors are detected earlier and more explicitly, making debugging faster and preventing silent failures from causing data integrity issues.

• Portability: Updating the shebang with /usr/bin/env ensures that scripts will run correctly on virtually any Linux distribution and Unix-like environment, including containers and custom systems.
• Error Prevention: The -u flag acts as a safety net against simple but potentially dangerous coding bugs related to variable expansion.

This action strengthens our codebase with high-quality shell scripting practices, ensuring greater reliability across various environments.