Http wrapper for Terraform CLI Part 1

OOB Hashicorp doesn’t offer an Terraform HTTP API/SDK for provisioning resources to cloud providers using terrafrom templates,(Their proprietary cloud does an awesome job of doing this).

However on the other hand Azure and AWS have an API (SDK) for provisioning resources using ARM and cloud formation templates.

For this POC i went ahead and created a wrapper for the terraform CLI to create an resource group in Azure.

The wrapper is written in Azure C# functions running locally, the second post of this series will cover the same functions running in Azure (hopefully).

The steps that i took are as follows

  1. Installed AZURE CLI and logged in.
  2. Created a Azure Functions Project
  3. Copied the terraform template, and the terraform cli into windows temp folder (C:\Users\<<username>>\AppData\Local\Temp)
  4. And the code is below and self explanatory, used the StartProcess method (and i did something similar Invoke Btstask from .net code – madhukar gilla ( in Dec 2010)
terraform {
  required_providers {
    azurerm = {
      source = "hashicorp/azurerm"
      version = "~>2.0"
provider "azurerm" {
  features {}

resource "azurerm_resource_group" "myterraformgroup" {
    name     = "myResourceGroup"
    location = "eastus"

    tags = {
        environment = "Terraform Demo"
using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.IO;
using System.Net.Http;
using System.Threading.Tasks;
using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Extensions.DurableTask;
using Microsoft.Azure.WebJobs.Extensions.Http;
using Microsoft.Extensions.Logging;
using Newtonsoft.Json;

namespace TerraformHttpWrapper
    public static class Function2
        public static async Task<List<string>> RunOrchestrator(
            [OrchestrationTrigger] IDurableOrchestrationContext context)
            var outputs = new List<string>();

            // Replace "hello" with the name of your Durable Activity Function.
            outputs.Add(await context.CallActivityAsync<string>("Function2_Hello", "Tokyo"));
            //outputs.Add(await context.CallActivityAsync<string>("Function2_Hello", "Seattle"));
            //outputs.Add(await context.CallActivityAsync<string>("Function2_Hello", "London"));

            // returns ["Hello Tokyo!", "Hello Seattle!", "Hello London!"]
            return outputs;

        public static string SayHello([ActivityTrigger] string name, ILogger log, ExecutionContext context)
            log.LogInformation($"Saying hello to {name}.");

            log.LogInformation("C# HTTP trigger function processed a request.");

            var tempRootDir = Path.GetTempPath();


            log.LogInformation($"----------------------------- Current directory { Directory.GetCurrentDirectory()} --------------------");
                Process p = new Process();
                p.StartInfo.UseShellExecute = false;
                p.StartInfo.FileName = "terraform.exe";
                p.StartInfo.Arguments = "init";
                p.StartInfo.RedirectStandardOutput = true;

                log.LogInformation("*****************************" + Environment.CurrentDirectory);


                log.LogInformation("----------------------------- DONE init --------------------");

                Process ptwo = new Process();
                ptwo.StartInfo.UseShellExecute = false;
                ptwo.StartInfo.FileName = "terraform.exe";
                ptwo.StartInfo.Arguments = "plan  -detailed-exitcode -lock=false";
                ptwo.StartInfo.RedirectStandardOutput = true;


                log.LogInformation("----------------------------- DONE plan --------------------");

                Process pthree = new Process();
                pthree.StartInfo.UseShellExecute = false;
                pthree.StartInfo.FileName = "terraform.exe";
                pthree.StartInfo.Arguments = "apply -auto-approve -lock=false";
                pthree.StartInfo.RedirectStandardOutput = true;



                log.LogInformation("----------------------------- DONE apply --------------------");

            catch (Exception ed)
                log.LogInformation("Error: ." + ed);

            return name;

        public static async Task<HttpResponseMessage> HttpStart(
            [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")] HttpRequestMessage req,
            [DurableClient] IDurableOrchestrationClient starter,
            ILogger log)
            // Function input comes from the request content.
            string instanceId = await starter.StartNewAsync("Function2", null);

            log.LogInformation($"Started orchestration with ID = '{instanceId}'.");

            return starter.CreateCheckStatusResponse(req, instanceId);

And the logs from the Azure Function and terraform cli are as follows.

Terrafrom and Azure Functions logs

And the created function group

ffmpeg, my favourite tool for audio editing.

As you know based on my previous posts that i recently bought a fitbit ionic for inbuilt GPS and music player, i have been using playerfm on mobile forever, one of the nice features of palyerfm is to increase/decrease the audio speed, and i am habituated to listening at 1.2x speed, now without these option in the native ionic music player, i had to fallback on editing the podcasts on my machine by using ffmpeg.

All you have to do is run the following cmd, use the atempo parameter to adjust the speed accordingly.

ffmpeg -i input.mp3 -filter:a “atempo=1.2” -vn output.mp3

its all worth it because i don’t have to carry my mobile phone for those long walks or jogs !!

Fitbit Ionic initial setup and firmware update…

Recently bought an Fitbit ionic, reason being

  1. I don’t need to carry a phone or another device for music and GPS.

the initial setup was a bummer thought of returning it back, the only way I could update the firmware was doing the following

  1.  Have 3g on the phone.
  2. Make the phone a hotspot
  3. Install the Fitbit app on Mac or windows(blue tooth).
  4. Add a new device and run the setup through the computer.
  5. Configure Fitbit WiFi to use to the Mobile Hotspot from step 2.
  6. And on the update configuration screen just select activity tracking, leave the others they will get automatically installed.

That’s it.. well then what combination did not work.

  1. With the app on windows configuring the Fitbit WiFi to use  Hotel/Home/Office WiFi did not work all were 2.4 GHz.
  2. Tried the same setup above with a phone instead of an windows box did not work.
  3. Tried both the above steps with Bluetooth instead of WiFi did not work.

Alll the best and post comments for any other information or questions.


I have been interviewing for a while, for my team for other teams…etc, most of the applicants are more than apt with their technical skills and logical reasoning, if you are still not sure about their technical skill set ask them to do a quick hands on exercise or ask them give a code walkthrough of their github project.

But how do we decide on who to hire? what we should be asking ourselves is “would I have him on my team” if you answer yes then nothing else matters just go ahead and select him. Technical skill can be worked upon if the applicant is a good fit for you team and yes apart from their skill set your gut feeling does matter.

Azure API Management Versions Vs Revisions

With the new Version and Revision features its confusing on when to use revisions or versions, my take is as follows

When should you use  Revisions:

  • If you want to do changes that are above your backend services, for example using policies.
    • Add authentication: your api did not have any authentication and you want to have one without disturbing your existing service, so you would add that in the in the new revision
    • Logging: you api did not have any logging of incoming and outgoing requests and you don’t want to disturb your backend service so you create a revision for that feature
  • Note: only 1 revision is exposed to the outside world

When should you use Versions:

  • Use versions when you introduce a breaking change in your api and deploy it as a new backend server and want to support both those deployments.

Increase Timeout for ASP.NET Core applications

Recently we came across a situation where in we had to increase the timeout of a aspnet web application, by default an aspnet core project does not generate a web.config file and did not find enough documentation on how to modify the appsetting.json file.


Google always ended up showing on how to do that in a web.config, which we did not have. After playing around we found that we could add a web.config to the solution



And add the following, there might be better ways of doing it, but wonder why Visual Studio (using 2017) does not add a web.config file automatically ?? maybe another blog post.


  1. <?xml version=“1.0” encoding=“utf-8”?>  
  2. <configuration>  
  4.   <!– To customize the core module uncomment and edit the following section.   
  5.   For more info see –>  
  7.   <system.webServer>  
  8.     <handlers>  
  9.       <remove name=“aspNetCore”/>  
  10.       <add name=“aspNetCore” path=“*” verb=“*” modules=“AspNetCoreModule” resourceType=“Unspecified”/>  
  11.     </handlers>  
  12.     <aspNetCore processPath=“%LAUNCHER_PATH%” arguments=“%LAUNCHER_ARGS%” stdoutLogEnabled=“false” stdoutLogFile=“.\logs\stdout”   
  13.                 requestTimeout=“00:20:00”/>  
  14.   </system.webServer>  
  16. </configuration>