Day4 of #90daysofdevops | Shell scripting

Explain in your own words and examples, what is Shell Scripting for DevOps.

What is #!/bin/bash? can we write #!/bin/sh as well?

Write a Shell Script that prints I will complete #90DaysOofDevOps challenge

Write a Shell Script to take user input, input from arguments and print the variables.

Write an Example of If else in Shell Scripting by comparing 2 numbers

1. What is Shell scripting for DevOps?
   Shell scripting is the process of creating and running scripts written in a shell language, such as Bash, on a Linux system. These scripts are used to automate repetitive tasks, manage system configurations, and facilitate the interaction between various components in a DevOps environment.

   In the context of DevOps, shell scripting plays a crucial role in streamlining and automating the deployment, management, and monitoring of applications and infrastructure. It enables developers and operations teams to effectively collaborate and ensure the smooth functioning of the software development lifecycle.

   Here are a few examples of how shell scripting can be beneficial in a DevOps setup:

   1. Deployment Automation: With shell scripting, you can create scripts that automate the deployment of applications, including setting up the required environment, configuring dependencies, and deploying the application code to multiple servers or containers. This helps in achieving consistent and reliable deployments, reducing human errors, and saving time.

   2. Configuration Management: Shell scripts allow you to define and manage system configurations, such as network settings, user accounts, software installations, and security configurations. By scripting these configurations, you can ensure consistency across different environments, making it easier to scale and manage your infrastructure.

   3. Continuous Integration and Delivery (CI/CD): Shell scripting plays a significant role in CI/CD pipelines. You can write scripts to build and test applications, package artifacts, trigger deployments, and perform automated quality checks. By automating these steps, you can achieve faster and more efficient software releases.

   4. Log Analysis and Monitoring: Shell scripts can be used to parse and analyze log files generated by applications and systems. You can write scripts to extract relevant information, detect anomalies, and trigger notifications or automated actions based on specific log patterns. This helps in proactively identifying and resolving issues in real-time.

   5. Data Manipulation and Processing: Shell scripting provides powerful tools for processing and manipulating data. You can write scripts to extract data from different sources, transform it into the required format, perform calculations, and generate reports or visualizations. This is particularly useful for tasks like log analysis, performance monitoring, and generating metrics.

In summary, shell scripting for DevOps empowers Linux admins and DevOps practitioners to automate tasks, manage configurations, streamline deployments, and enhance monitoring and analysis. It enables more efficient and reliable operations, freeing up time for teams to focus on innovation and continuous improvement.

1. What is #!/bin/bash? can we write #!/bin/sh as well?

   In Linux and Unix-like operating systems, the line "#!/bin/bash" is known as a shebang or hashbang. It is placed at the beginning of a script file and is used to specify the interpreter or shell that should be used to execute the script.

   The shebang line "#!/bin/bash" specifically indicates that the Bash shell should be used to interpret and execute the script. Bash (short for "Bourne Again SHell") is a popular and powerful shell that is widely available on Linux systems. It provides numerous features and extensions to the original Bourne shell, making it a versatile choice for scripting.

   On the other hand, "#!/bin/sh" indicates that the script should be executed using the system's default shell. In most Linux distributions, "/bin/sh" is typically a symbolic link to the default shell, which could be Bash, Dash (Debian Almquist Shell), or another shell depending on the distribution. However, it is important to note that "/bin/sh" may vary across different systems or distributions, and it is not guaranteed to be Bash.

   So, to answer your question, yes, you can write "#!/bin/sh" instead of "#!/bin/bash" if you want the script to be executed using the default shell. However, it's worth considering that using "#!/bin/bash" provides you with the additional features and capabilities of Bash, which may be beneficial for more complex or advanced scripting requirements.

   In general, if your script relies on Bash-specific features or syntax, it's recommended to use "#!/bin/bash" to ensure compatibility. On the other hand, if your script is simpler and doesn't require any specific Bash features, using "#!/bin/sh" can make it more portable across different systems that may have a different default shell.

2. Write a Shell Script that prints I will complete #90DaysOofDevOps challenge

   

3. Write a Shell Script to take user input, input from arguments and print the variables.

   Here, changing the permission of the file is important, which can be done by chmod command, also we need to make our file executable by ./<file name>

   

4. Write an Example of If else in Shell Scripting by comparing 2 numbers

Conclusion and key points:

What is Kernel?

The kernel is a computer program that is the core of a computer’s operating system, with complete control over everything in the system.

What is Shell?

A shell is a special user program that provides an interface for the user to use operating system services. Shell accepts human-readable commands from users and converts them into something which the kernel can understand. It is a command language interpreter that executes commands read from input devices such as keyboards or from files. The shell gets started when the user logs in or start the terminal.

Thanks for reading the blog & do share them with someone in need :)

Please share your views and suggestions, they are always welcome.

See you then in the next blog.

Happy learning :)