Creating Service Accounts is an especially tedious process when we need to create a lot of those for different purposes, mainly driven by the least privilege access across environments, projects, deployments or simply different clients. So why don’t improve this? Let’s make it all more fun, efficient and less error-prone, so let’s automate it! Continue reading “How to Create New Service Accounts in Active Directory from a CSV with Powershell”
Once again this is not a sponsored review by my 2 cents.
This pocket guide it’s not an introduction on git the best practices, but it will show some options available and will boost your confidence and knowledge to solve most of the common problems. It’s full of practical examples with just enough deep dive into git to show you the things work under the hood.
This book is very good “to show you the tip of the iceberg”. Git, like any other distributed systems it’s complex, but most of its common features and operations are easy to understand aren’t so difficult and if you’re not familiar with the cli, there are plenty of tools to get you started. Continue reading “Git Pocket Guide”
As a DevOps engineer, I frequently come across talented developers that underestimate some security aspects of the deployments, for instance, just to name a couple: integrity and authenticity of the code or artefacts that we deploy.
Python and Powershell are powerful languages to develop quick and robust solutions are extremely popular between attackers, for this reason, our ecosystem should take security very seriously.
Security is now far beyond the (old) perimeter of the company’s premises and infrastructure, indeed network or systems is abstracted away with or without cloud/hybrid deployments and just the enforcing identity is not enough in most cases.
In my opinion, white-listing applications around code-signing and checking the integrity of our code it’s more effective and less painful than you can think a good habit to build on a daily basis.
As a DevOps, most of my energies are constantly focused on doing or fixing things right from the start with the intention of creating a simple or at least straightforward processes. But this is not an article on my endless war against technical debt and avoiding shortcuts whenever it’s possible.
the more things change, the more they stay the same
The values and the culture inherited from ITIL, Agile and DevOps massively influenced the whole modern software life cycle. CI/CD extended to code quality/testing/delivery etc.. In these years should have changed most of our daily tasks or our business-as-usual, right? Well… not yet! Continue reading “Application Deployment Troubleshooting with Powershell”
As a DevOps with work experiences as a Developer and System Engineer, I tend to give for granted that all my colleagues or peers have the same background knowledge or simply the same vocabulary.
But I’ve recently discussed with some seasoned sysadmins working for other companies and I was surprised to discover the barrier was around the vocabulary and the design principles (for developers or system engineers) used as a reference point.
Naturally, we try to solve problems with solutions or technologies that we already used in the past, without exploring all the possibilities. Sometimes we simply don’t get some context or benefits of doing it differently or we can’t measure how expensive can be the adoption of different models or strategies.
For instance: Microservices, RESTfulAPI, Webhooks are common terms that most of us are comfortable using every day, but these design implementations and functions are sometimes not so simple to break it down into small independent pieces. Continue reading “How to trigger incoming webhooks in Microsoft Teams with Powershell”