Skip to main content

· 10 min read

Instead of defining the raw infrastructure we need, hamlet works off a solution. The solution outlines the functional components required in the deployment and hamlet then takes this to build out the infrastructure definition that would perform this function.

Combining this with our pluggable architecture we can use the same solution to generate infrastructure definitions in different cloud providers like AWS and Azure. This is an interesting feature itself but in this post we are going to look at another way to use this data, diagram generation.

· 12 min read

Static websites are everywhere nowadays, alongside them on their rise in popularity are the numerous app frameworks like Jekyll, Gatsby and Docusaurus that allow anyone to spin up and deploy documentation, a blog or simple website, often for for little or no cost.

· 11 min read

hamlet has its own opinions on how things should be done. These opinions are formed by our community based on best practice ( including the best way to workaround things ) to get you working in the cloud as efficiently as possible. Sometimes you might want to try out something new that we don't support or a component we offer isn't quite right. In this series of posts, Prototyping Deployments you should get an idea of how hamlet helps with these deployments and integrates with the rest of your solution.

· 17 min read

Welcome to our first release of 2021, we've been a bit late on our releases so this one has a lot of changes. We will touch on the highlights here and you can discover the rest in our new repo changelogs

· 8 min read

So far in our blog series we’ve covered off the basics that show you how hamlet is used to create ARM templates. Today we’re going to go even further and show you how hamlet is able to take an existing provider and extend its capabilities into orchestration. We’re also going to take a look at how hamlet addresses some of the more frustrating parts of cloud deployments - obscure naming conventions across resources.

· 7 min read

Today we'll be showcasing the db hamlet component through the lens of the Azure Resource Manager (ARM) templates. Generated by the Azure provider engine plugin for hamlet, this example serves to illustrate not just how the Azure plugin implements this common component but more broadly how hamlet is able to adapt to each provider without becoming overly generic in function. Making use of some of the more advanced provider-specific template features here, we'll also cover how hamlet is used to perform utility actions before and after a deployment, filling some of the orchestration gaps typical of Infrastructure-as-Code.

· 8 min read

Welcome to the start of a new series of blog posts centred around the hamlet Azure provider. In each article will showcase a new hamlet component type and how it has been implemented by the Azure provider plugin. Along the way we'll review some unique Infrastructure-as-Code challenges that hamlet addresses as well as deep dive into some of its features.

· 13 min read

Welcome to hamlet! One big part of this release is our rename from codeontap to hamlet. Along with the rename we have also introduced deployment profiles and a new CMDB layout