Book Image

PowerShell Core for Linux Administrators Cookbook

By : Prashanth Jayaram, Ram Iyer
Book Image

PowerShell Core for Linux Administrators Cookbook

By: Prashanth Jayaram, Ram Iyer

Overview of this book

PowerShell Core, the open source, cross-platform that is based on the open source, cross-platform .NET Core, is not a shell that came out by accident; it was intentionally created to be versatile and easy to learn at the same time. PowerShell Core enables automation on systems ranging from the Raspberry Pi to the cloud. PowerShell Core for Linux Administrators Cookbook uses simple, real-world examples that teach you how to use PowerShell to effectively administer your environment. As you make your way through the book, you will cover interesting recipes on how PowerShell Core can be used to quickly automate complex, repetitive, and time-consuming tasks. In the concluding chapters, you will learn how to develop scripts to automate tasks that involve systems and enterprise management. By the end of this book, you will have learned about the automation capabilities of PowerShell Core, including remote management using OpenSSH, cross-platform enterprise management, working with Docker containers, and managing SQL databases.
Table of Contents (19 chapters)

Defining arguments for a script

Scripts help with a good amount of automation. Most administrators that I have come across like to create self-contained scripts. However, this means that you have to hardcode a lot of information that you may not want someone to read, such as passwords or keys. This is a limitation with scripts that contain everything in them. Of course, another way to handle such a situation is to use secure files such as a CLI XML with the password or key stored as a secure string, which will work only on that computer, only with your sign-in. But then, what if someone else wanted to use your script with their credentials?

You get the point. Hardcoding certain things is not a very flexible way to do this—it kills modularity. The other option available to us is to prompt the user for such information. But what if you were writing a script to be used unattended...