The term Interlok Hammer came about when our chief architect was describing a consultants use of the Interlok product as a solution for a client.
The use case being an Interlok adapter receiving signed instances of system-command-executor service to dynamically execute arbitrary system commands to provision processing units.
And with that a phrase was born…
It started as an internal joke, but it made me realise something. The combination of the products ability to chain together arbitrary actions and a person’s pragmatic approach to problem solving, will eventually produce things far from what the product was ever intended to do. Which for me is one of those times I use the word cool (arguably incorrectly)!
More and more use cases will pop up from our customers, consultants, and developers (some may end up on GitHub or this blog). There’s also a tongue in cheek badge, created for projects to wear with pride:
Some of my favourite examples of Interlok Hammers are:
- One that replies to your email with data you requested (Blog post)
- Another that manages your DevOps pipeline for your Interlok config (Blog post)
- Another that stores speed test results in elastic search (GitHub project)