Book Image

Learn PowerShell Core 6.0

By : David das Neves, Jan-Hendrik Peters
Book Image

Learn PowerShell Core 6.0

By: David das Neves, Jan-Hendrik Peters

Overview of this book

Beginning with an overview of the different versions of PowerShell, Learn PowerShell Core 6.0 introduces you to VSCode and then dives into helping you understand the basic techniques in PowerShell scripting. You will cover advanced coding techniques, learn how to write reusable code as well as store and load data with PowerShell. This book will help you understand PowerShell security and Just Enough Administration, enabling you to create your own PowerShell repository. The last set of chapters will guide you in setting up, configuring, and working with Release Pipelines in VSCode and VSTS, and help you understand PowerShell DSC. In addition to this, you will learn how to use PowerShell with Windows, Azure, Microsoft Online Services, SCCM, and SQL Server. The final chapter will provide you with some use cases and pro tips. By the end of this book, you will be able to create professional reusable code using security insight and knowledge of working with PowerShell Core 6.0 and its most important capabilities.
Table of Contents (26 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Challenges of DevOps


There are a couple of challenges that you will encounter or have to overcome when it comes to DevOps. The challenge we mostly see when working with customers involves issues in the communication between teams. This stems from the issue that silos are in fact not busted, but every silo simply develops their own set of DevOps practices and carries on.

Communication is key when starting with DevOps. It is easy to say that Dev and Ops need to get closer together. In practice, this is not a simple task at all. Communication does not just mean getting people to talk to each other and to collaborate. It also means agreeing on tools to use, development philosophies to follow, and so on.

Another challenge that is commonly encountered—not only due to a lack of communication—is a lack of consistent tooling. If every team does what they want and deploys the tool they want, silos continue to exist.

The result of this will be utter chaos. If the tool landscape is too fragmented, there...