<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://lindnerbrewery.github.io/</id><title>LindnerBrewery</title><subtitle>PowerShell and IT stuff</subtitle> <updated>2024-09-29T15:56:41+00:00</updated> <author> <name>Emrys MacInally</name> <uri>https://lindnerbrewery.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://lindnerbrewery.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://lindnerbrewery.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.3.4">Jekyll</generator> <rights> © 2024 Emrys MacInally </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Connecting VSCode to an AWS EC 2 Instance via SSM</title><link href="https://lindnerbrewery.github.io/posts/Connecting_VSCode_to_an_AWS_EC_2_Instance_via_SSM/" rel="alternate" type="text/html" title="Connecting VSCode to an AWS EC 2 Instance via SSM" /><published>2024-09-28T00:00:00+00:00</published> <updated>2024-09-29T15:56:22+00:00</updated> <id>https://lindnerbrewery.github.io/posts/Connecting_VSCode_to_an_AWS_EC_2_Instance_via_SSM/</id> <content src="https://lindnerbrewery.github.io/posts/Connecting_VSCode_to_an_AWS_EC_2_Instance_via_SSM/" /> <author> <name>Emrys MacInally</name> </author> <summary> Lately, I’ve been working on a project that requires using AWS, and we have an EC2 instance that doesn’t have port 22 open to the internet. Additionally, there’s no VPN set up to access the VPC. Fortunately, AWS Systems Manager (SSM) allows us to access and manage our resources without exposing them to the internet or needing a VPN. While it’s easy to get console access to an EC2 instance using... </summary> </entry> <entry><title>Converting conventional version to semantic version with PowerShell</title><link href="https://lindnerbrewery.github.io/posts/converting_to_semtantic_version/" rel="alternate" type="text/html" title="Converting conventional version to semantic version with PowerShell" /><published>2024-01-05T00:00:00+00:00</published> <updated>2024-01-08T12:47:53+00:00</updated> <id>https://lindnerbrewery.github.io/posts/converting_to_semtantic_version/</id> <content src="https://lindnerbrewery.github.io/posts/converting_to_semtantic_version/" /> <author> <name>Emrys MacInally</name> </author> <summary> Lately I’ve been needing to validate and convert versions to semantic versions. For instance, a version defined as “23.01” needed to be converted to “23.1.0”. This led me to create a PowerShell function, ConvertTo-SemVersion, made to transform a conventional version numbers into the semantic versioning format. What is Semantic Versioning? Semantic Versioning (SemVer) is a versioning scheme fo... </summary> </entry> <entry><title>Versioning PowerShell modules with GitVersion in Mainline Mode</title><link href="https://lindnerbrewery.github.io/posts/GitVersion_Mainline/" rel="alternate" type="text/html" title="Versioning PowerShell modules with GitVersion in Mainline Mode" /><published>2023-11-11T00:00:00+00:00</published> <updated>2024-01-05T16:32:20+00:00</updated> <id>https://lindnerbrewery.github.io/posts/GitVersion_Mainline/</id> <content src="https://lindnerbrewery.github.io/posts/GitVersion_Mainline/" /> <author> <name>Emrys MacInally</name> </author> <summary> In the world of software development, version management is a critical aspect of maintaining the integrity of a project and tracking its progress. For PowerShell module developers, the process of versioning can sometimes be a manual and error-prone task. In this blog post, we’ll explore an alternative approach to versioning using GitVersion in mainline mode, which can help streamline the proces... </summary> </entry> <entry><title>Restarting Octopus Deploy Tentacle during a deployment</title><link href="https://lindnerbrewery.github.io/posts/restart_tentacle/" rel="alternate" type="text/html" title="Restarting Octopus Deploy Tentacle during a deployment" /><published>2023-09-04T00:00:00+00:00</published> <updated>2023-09-04T00:00:00+00:00</updated> <id>https://lindnerbrewery.github.io/posts/restart_tentacle/</id> <content src="https://lindnerbrewery.github.io/posts/restart_tentacle/" /> <author> <name>Emrys MacInally</name> </author> <summary> When deploying an Octopus project, one of your steps may involve editing or creating an environment variable. One of the most common variables to be updated when installing an application is the PATH variable. An installation adds the folder where the application can be found to the PATH variable. In other cases, an application will create a new environment variable. Java, for example, will cr... </summary> </entry> <entry><title>Retrieving values of sensitive variables in Octopus Deploy</title><link href="https://lindnerbrewery.github.io/posts/retrieve_sensitive_vars/" rel="alternate" type="text/html" title="Retrieving values of sensitive variables in Octopus Deploy" /><published>2023-08-04T00:00:00+00:00</published> <updated>2023-08-04T14:05:03+00:00</updated> <id>https://lindnerbrewery.github.io/posts/retrieve_sensitive_vars/</id> <content src="https://lindnerbrewery.github.io/posts/retrieve_sensitive_vars/" /> <author> <name>Emrys MacInally</name> </author> <summary> When working with variables in Octopus Deploy, you want to keep passwords or API keys secret and out of sight. Octopus offers “sensitive variables” for this use case. Sensitive variables are stored encrypted in the database and cannot be retrieved once set. In the UI or deployment logs the variables will only appear as *******. If, like me, you manage to set a sensitive variable and forget to... </summary> </entry> </feed>
