Wonder woman geek

  I am a big fan of Azure Pipelines (and Azure DevOps). Being one for years. Azure Pipelines is a very mature and powerful tool. Azure DevOps/Pipelines was built with the enterprise in mind and it works really well for the enterprise world. It allows you to create workflows that automatically build, test, publish, release, and deploy code to provide end-to-end traceability of the software development lifecycle. . Then, out of the blue, Microsoft buys GitHub in 2018 and starts immediately expanding GitHub functionality. Over last two years, there have been so much innovation and improvement in GitHub functionality: advanced security, secret scanning, package management, codespaces, insights, dependabots, projects, innersource management, and of course, GitHub Actions. There is so much awesomeness to cover! But, let’s stay focused on GitHub Actions for now (and, perhaps, cover other items in future posts.) GitHub Actions is an excellent CICD tool to automate your software workflows t...

The need to manage multiple GitHub accounts on the same machine comes up at some point in time for most developers. Every single time I happen to change my Mac or need to Git push with a new work account, I end up surfing for the how to’s of something I have done over half a dozen times. My laziness in not documenting the process and inability to remember the steps makes me spent a decent amount of time getting the bits and pieces from all over the web and then somehow making it work. I’m sure there are many of you who have been there, done that and many more of you who are just waiting for the next time the same thing occurs (myself included!). This endeavor is meant to help us all out. 1. Generating the SSH keys Before generating an SSH key, we can check to see if we have any existing SSH keys:  ls -al ~/.ssh  This will list out all existing public and private key pairs, if any. If  ~/.ssh/id_rsa  is available, we can reuse it, or else we can first generate a key t...

Both CloudTrail and Activity Logs record the configuration changes made to an AWS account or Azure subscription respectively. However, while CloudTrail can be enabled or disabled per region, Activity Logs are a global record for the entire subscription. CloudTrail logs a trail of management and configuration events to an S3 bucket in your account, so you can encrypt using KMS, and also the logs can potentially be manipulated, hence the optional feature to verify logs using a digest. Azure Activity log is a centralised record stored by Microsoft, so doesn’t appear in any of your Azure Storage buckets, there’s no option for encryption using KMS, and no need for a digest feature (at least, none that’s visible to the customer). You can’t disable Azure Activity logs, and after 90 days, the logs can no longer be viewed. To keep logs older than 90 days, Azure Activity logs can be archived in Azure Storage, streamed to Event Hub, or sent to a Log Analytics workspace. Any of these methods ca...

Cloud logging enables you to centrally manage log data collected from multiple cloud resources. Log data is essential for measuring and optimizing cloud performance and security. However, it can be extremely difficult to effectively leverage log data from complex multi-cloud architectures. Often, simplicity and granular visibility are critical for ensuring efficient cloud logging. In this post, we’ll examine key components any multi-cloud logging strategy should account for, including tips for choosing tooling, determining structure, and creating logging processes.  What Is Cloud Logging? Cloud logging is a practice that enables you to collect and correlate log data from cloud applications, services, and infrastructure. It is performed to help identify issues, measure performance, and optimize configurations. Cloud logging relies on the creation of log files, collections of data that document events occurring in your systems. Log files can contain a wide variety of data, including ...