Forem: Rakesh Suryawanshi

Terraform Plan Command

Rakesh Suryawanshi — Tue, 16 Aug 2022 21:54:00 +0000

This is Part-04 of Developer's Guide to Terraform in this section we are going to discuss about the Terraform Plan Command.

Terraform plan

The terraform plan command creates an execution plan, which lets you preview the changes that Terraform plans to make to your infrastructure. By default, when Terraform creates a plan it:

Reads the current state of any already-existing remote objects to make sure that the Terraform state is up-to-date.
Compares the current configuration to the prior state and noting any differences.
Proposes a set of change actions that should, if applied, make the remote objects match the configuration.

Terraform Init Command

Rakesh Suryawanshi — Tue, 16 Aug 2022 20:44:00 +0000

This is Part-03 of Developer's Guide to Terraform in this section we are going to discuss about the Terraform Commands.

As we know that terraform is command line tool like git, Kubernetes, this means that terraform also gets operated with its command line like we operate git or Kubernetes with command line.

Terraform also offers various commands which you can use... to know the list of command name you can use terraform help command

🦄  terraform -h
Usage: terraform [global options] <subcommand> [args]

The available commands for execution are listed below.
The primary workflow commands are given first, followed by
less common or more advanced commands.

Main commands:
  init          Prepare your working directory for other commands
  validate      Check whether the configuration is valid
  plan          Show changes required by the current configuration
  apply         Create or update infrastructure
  destroy       Destroy previously-created infrastructure

All other commands:
  console       Try Terraform expressions at an interactive command prompt
  fmt           Reformat your configuration in the standard style
  force-unlock  Release a stuck lock on the current workspace
  get           Install or upgrade remote Terraform modules
  graph         Generate a Graphviz graph of the steps in an operation
  import        Associate existing infrastructure with a Terraform resource
  login         Obtain and save credentials for a remote host
  logout        Remove locally-stored credentials for a remote host
  output        Show output values from your root module
  providers     Show the providers required for this configuration
  refresh       Update the state to match remote systems
  show          Show the current state or a saved plan
  state         Advanced state management
  taint         Mark a resource instance as not fully functional
  test          Experimental support for module integration testing
  untaint       Remove the 'tainted' state from a resource instance
  version       Show the current Terraform version
  workspace     Workspace management

Global options (use these before the subcommand, if any):
  -chdir=DIR    Switch to a different working directory before executing the
                given subcommand.
  -help         Show this help output, or the help for a specified subcommand.
  -version      An alias for the "version" subcommand.

With above result you can see that terraform has various commands which you can use to manage your infrastructure but to begin with terraform to automate your infrastructure you may not need to know all of these, in this blog we will discuss what all commands you need to know to provision Infrastructure with terraform.

Terraform Init

The terraform init command is used to initialize a working directory containing Terraform configuration files. This is the first command that should be run after writing a new Terraform configuration or cloning an existing one from version control. It is safe to run this command multiple times.

Usage

terraform init [options]

🦄  terraform init -h
Options:

  -backend=false          Disable backend or Terraform Cloud initialization for
                          this configuration and use what what was previously
                          initialized instead.

                          aliases: -cloud=false

  -backend-config=path    Configuration to be merged with what is in the
                          configuration file's 'backend' block. This can be
                          either a path to an HCL file with key/value
                          assignments (same format as terraform.tfvars) or a
                          'key=value' format, and can be specified multiple
                          times. The backend type must be in the configuration
                          itself.

  -force-copy             Suppress prompts about copying state data when
                          initializating a new state backend. This is
                          equivalent to providing a "yes" to all confirmation
                          prompts.

  -from-module=SOURCE     Copy the contents of the given module into the target
                          directory before initialization.

  -get=false              Disable downloading modules for this configuration.

  -input=false            Disable interactive prompts. Note that some actions may
                          require interactive prompts and will error if input is
                          disabled.

  -lock=false             Don't hold a state lock during backend migration.
                          This is dangerous if others might concurrently run
                          commands against the same workspace.

  -lock-timeout=0s        Duration to retry a state lock.

  -no-color               If specified, output won't contain any color.

  -plugin-dir             Directory containing plugin binaries. This overrides all
                          default search paths for plugins, and prevents the
                          automatic installation of plugins. This flag can be used
                          multiple times.

  -reconfigure            Reconfigure a backend, ignoring any saved
                          configuration.

  -migrate-state          Reconfigure a backend, and attempt to migrate any
                          existing state.

  -upgrade                Install the latest module and provider versions
                          allowed within configured constraints, overriding the
                          default behavior of selecting exactly the version
                          recorded in the dependency lockfile.

  -lockfile=MODE          Set a dependency lockfile mode.
                          Currently only "readonly" is valid.

  -ignore-remote-version  A rare option used for Terraform Cloud and the remote backend
                          only. Set this to ignore checking that the local and remote
                          Terraform versions use compatible state representations, making
                          an operation proceed even when there is a potential mismatch.
                          See the documentation on configuring Terraform with
                          Terraform Cloud for more information.

Let's look at various parameter option with terraform init command

1. Terraform init with backend

If you have terraform provider block with empty backend blocked specified like this

terraform {
  required_providers {
    azurerm = {
      version = "~> 2.88.1"
      source = "hashicorp/azurerm"
    }
  }
  backend "azurerm" {
  }
}

Then you need to specify the backend at the time of initialization of terraform from terraform init command, to do that you can run terraform init with backend-config option

terraform init -backend-config=storage_account_name=tfstatefile01 -backend-config=container_name=tfstate -backend-config=key=dev-network.terraform.tstate -backend-config=resource_group_name=DefaultResourceGroup-EUS -backend-config=subscription_id=2a04288a-8136-4880-b526-c6070e59f004 -backend-config=tenant_id=37d20c78-05e3-416d-83ab-cdbc21fed22a -backend-config=client_id=*** -backend-config=client_secret=***

As you can see terraform backend-config parameter multiple times.

Here with terraform init we are specifying following terraform backend configuration

azure backend storage account name
azure backend storage account resource group name
azure backend storage account container name
azure subscription Id
azure tenant id
azure service principal client Id
azure service principal client secret

It is also possible that partial configuration you specify in terraform code block and partial with terraform init backend-config parameters.

NOTE
If your terraform backend block is defined empty as given above then backend configuration must requires to specify at terraform init command otherwise it will throw an error

🦄  terraform init
Initializing modules...

Initializing the backend...
container_name
  The container name.

  Enter a value:

key
  The blob key.

  Enter a value:

storage_account_name
  The name of the storage account.

  Enter a value:

╷
│ Error: obtaining Authorization Token from the Azure CLI: parsing json result from the Azure CLI: waiting for the Azure CLI: exit status 1: ERROR: AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2022-07-28T06:34:30.5567960Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2022-08-16T19:33:00.0000000Z'.

2. Terraform Init without backend

Now let's say we have terraform provider defined with empty backend and we still would like to run terraform init command without terraform backend then you can do that with backend=false option.

Here is the command

terraform {
  required_providers {
    azurerm = {
      version = "~> 2.88.1"
      source = "hashicorp/azurerm"
    }
  }
  backend "azurerm" {
  }
}

🦄  terraform init -backend=false
Initializing modules...

Initializing provider plugins...
- Reusing previous version of hashicorp/azurerm from the dependency lock file
- Reusing previous version of aztfmod/azurecaf from the dependency lock file
- Using previously-installed hashicorp/azurerm v2.88.1
- Using previously-installed aztfmod/azurecaf v1.2.18

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

3. Disable Input action with Terraform Init

By default if you run terraform init it will ask for the backend configuration as prompt, if you want you can disable the prompt option using input=false option

NOTE
Disabling interactive prompts give some error if input is disabled

That's it for now, there are some other options also available with terraform init command which we can take at look at later in some other section.

Next we will look at terraform plan command.

For loop with liquid template in Azure LogicApp

Rakesh Suryawanshi — Thu, 04 Aug 2022 18:12:00 +0000

In this blog I will share how to use for loop with liquid templates.

Introduction
When to use?
For loop

Introduction
Liquid is a template language created by Shopify. It's available as an open source project on GitHub, and is used by many different software projects and companies.
more information can be found here.

When to use?
Liquid templates are great tool to bind your UI with XML or json response, additionally you can use these in your Azure Integration services such as logic apps or Azure API management.

recently I have used the liquid template with various scenarios.

documentation to learn liquid templates can be found here.

https://shopify.github.io/liquid/basics/introduction/

For loop
Let's learn how to write loops using Liquid template in various conditions.

Loop all Item of an Array

[
 "apple",
 "mango"
 "banana"
]

"fruits" :[
{% for item in content %}
  {
    "name": "{{item}}"
  }
{% if forloop.last == false %},{% endif %}
{% endfor %}

Loop over all items in a collection backwards

[
 "apple",
 "mango"
 "banana"
]

Here we can use reversed keyword to revers the Item of an array.

"fruits" :[
{% for item in content reversed %}
  {
    "name": "{{item}}"
  }
{% if forloop.last == false %},{% endif %}
{% endfor %}

Loop over a sorted collection

[
 "apple",
 "mango"
 "banana"
]

Here we can use sort keyword with pipe character (|) to sort the element of an array.

"fruits" :[
{% for item in  (content | sort) %}
  {
    "name": "{{item}}"
  }
{% if forloop.last == false %},{% endif %}
{% endfor %}

Loop a certain number of times

{% for i in (0..4) %}
   Iteration {{ i }}
{% endfor %}

Loop a variable number of times

{$ assign start = 0 %}
{% assign end = 4 %}
{% for i in (start..end) %}
   Iteration {{ i }}
{% endfor %}

**
Loop a certain number of times backwards**

{% for i in (0..4) reversed %}
   Iteration {{ i }}
{% endfor %}

Loop over an arbitrary range of integers

{% for i in (-3..3) %}
Iteration {{ i }}
{% endfor %}

Loop over the first 5 items in a collection

[
 "apple",
 "mango"
 "banana",
 "Avocados",
 "Cherry",
 "Blueberries"
]

Here we can use limit keyword to limit the Item of an array.

"fruits" :[
{% for item in content | limit: 5 %}
  {
    "name": "{{item}}"
  }
{% if forloop.last == false %},{% endif %}
{% endfor %}

Loop over the first 5 items in a collection in reverse order

[
 "apple",
 "mango"
 "banana",
 "Avocados",
 "Cherry",
 "Blueberries"
]

Here we can use reversed keyword to revers the Item of an array.


{% assign rev_content  = content | reverse %}
"fruits" :[
{% for item in rev_content | limit: 5 %}
  {
    "name": "{{item}}"
  }
{% if forloop.last == false %},{% endif %}
{% endfor %}

Do something special on the Nth iteration of the loop

[
 "Sunday",
 "Monday"
 "Tuesday",
 "Wednesday",
 "Thursday",
 "Friday",
 "Saturday"
]

Here we can use reversed keyword to revers the Item of an array.


{% for d in content %}
{{ forloop.index }}
{% if forloop.first %}st
{% elsif forloop.index == 2 %}nd
{% elsif forloop.index == 3 %}rd
{% else %}th{% endif %}
 day is {{ d }}
{% endfor %}

That's it I hope you will find this useful.

Thanks!! 🍻🍻🍻🍻.

Loops Conditions with Azure Logic Apps

Rakesh Suryawanshi — Wed, 20 Jul 2022 10:01:52 +0000

Loops Conditions with Azure Logic Apps

Azure Logic Apps Basic

Rakesh Suryawanshi — Wed, 20 Jul 2022 10:01:32 +0000

Azure Logic Apps Basic... Content to be added

Subscribe to GCP Topic in Azure from C#

Rakesh Suryawanshi — Tue, 28 Jun 2022 08:32:25 +0000

Today in this Blog I would like to share

How to subscribe google cloud publisher subscriber (Pubsub) topics into Azure services (azure function) using Microsoft visual studio C#

Overview
Pub/Sub is an asynchronous messaging service designed to be highly reliable and scalable. The service is built on a core Google infrastructure component that many Google products have relied upon for over a decade. Google products including Ads, Search and Gmail use this infrastructure to send over 500 million messages per second, totaling over 1TB/s of data. This article describes the salient design features that enables Pub/Sub to provide this type of scale reliably.

The Basics of a Publish/Subscribe Service
Pub/Sub is a publish/subscribe (Pub/Sub) service: a messaging service where the senders of messages are decoupled from the receivers of messages. There are several key concepts in a Pub/Sub service:

Message: the data that moves through the service.

Topic: a named entity that represents a feed of messages.

Subscription: a named entity that represents an interest in receiving messages on a particular topic.

Publisher (also called a producer): creates messages and sends (publishes) them to the messaging service on a specified topic.

Subscriber (also called a consumer): receives messages on a specified subscription.

The following diagram shows the basic flow of messages through Pub/Sub:

Publishers A and B push a message to a single topic, where two subscriptions listen for messages and push them to multiple subscribers.

In this scenario, there are two publishers publishing messages on a single topic. There are two subscriptions to the topic. The first subscription has two subscribers, meaning messages will be load-balanced across them, with each subscriber receiving a subset of the messages. The second subscription has one subscriber that will receive all of the messages. The bold letters represent messages. Message A comes from Publisher 1 and is sent to Subscriber 2 via Subscription 1, and to Subscriber 3 via Subscription 2. Message B comes from Publisher 2 and is sent to Subscriber 1 via Subscription 1 and to Subscriber 3 via Subscription 2

Prerequisites
Now as we have some idea about the architecture of this google service, let's create a topic in google cloud.

first you need to have google cloud account where we can create a GCP topic and subscriber.

You can register free with your gmail account to create a google cloud account.

Once you have google cloud account you can login to cloud console using this URL

By default a google cloud project will be created, you create a new one using Project drop down

Once you are in your project you can select Pubsub service from the left menu bar

Or you can search on top search bar with keyword "Topic"

Once you select the Pubsub service you will be navigated to Topic service Dashboard where you can find all the created topics and it's details.

Create Topic
To create new topic click on Create Topic button

Once you create a topic a default subscription will be created.

Now let's publish a new message to this topic manually (in your actual application it might possible some process will publish a message)

click on message tab

Now on the dashboard you can select subscription (default one in this case) and view the messages

Next we requires to create a service account and role to access the Pubsub service

Create Service account

To create a Service Account search IAM in the top search bar select IAM

Select Service account option from the left menu, Click on 'Create new Service Account' button to create a new service account.

Enter the detail and click on Create Account and Proceed

Select Role

Select Pub/Sub Publisher and Pub/Sub Subscriber

Click on Continue and click 'Done' (Don't make any changes to Grant users access to this service account option)

after this an account will be created now we need to create a Key for this service account

Select service account and click on Key tab

Click on 'Add Key' button to add new key for this service account

This will save a private key on your work station

This is the key which you can use in your program




{
  "type": "service_account",
  "project_id": "xenon-raceway-268218",
  "private_key_id": "9620fb3dd81a33e2bbe0e8defd327858633459ef",
  "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC2Brf0+VVIv2vs\nUVAUSPKiP57z/9NOp/7qJyVgJsnk7brqvpU7RiJpCF84wmp4Emlgxh3vbwZa2+BU\n9MtCcd3Xb4JVnA0dxSafRIRQE6Fljp8KtKk42VZg2mggwdHhCXO1wfCbWtd5yng6\nIGV0OxWlzQbATmk+HvHZoOVZ1bWv22Baf2rF5w3msj9i4Jh5wU8fAQHX9+oWEVJRGCEZslB\nJ+vaWVVYluxfDpmv7YCZ3gs=\n-----END PRIVATE KEY-----\n",
  "client_email": "spn-pub-sub@xenon-raceway-268218.iam.gserviceaccount.com",
  "client_id": "116457436621716168449",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/spn-pub-sub%40xenon-raceway-268218.iam.gserviceaccount.com"
}

This json is the one which will be used to in the program to access to service data.

You can find more details about the environment variables here



https://cloud.google.com/docs/authentication/getting-started

Using above mentioned steps you can complete the setup of your Infra structure for PubSub topic

Lets create a new Console application or azure function application with C# as language

The code requires to use google cloud C# SDK using the NuGet packages

Now you can write azure function code to write following code to read the message from service topic from google.



Environment.SetEnvironmentVariable("GOOGLE_APPLICATION_CREDENTIALS", Path.Combine(Environment.CurrentDirectory, "credentials.json"));
    string projectId = "xenon-raceway-268218";
    string topicId = "order-topic";
    string subscriptionId = "order-topic-sub";
    ProjectName projectName = ProjectName.FromProject(projectId);

    var subscriptionName = new SubscriptionName(projectId, subscriptionId);
    while (true)
    {
        var subscriber = await SubscriberClient.CreateAsync(subscriptionName);
        try
        {
            await subscriber.StartAsync((msg, ct) =>
            {
                Console.WriteLine(msg.Data.ToStringUtf8());
                return Task.FromResult(SubscriberClient.Reply.Ack);
            });
        }
        catch (Exception e)
        {
            Console.WriteLine($"Exception: {e}");
        }
    }

This is how the output will looks like

References

https://cloud.google.com/pubsub/docs/reference/libraries#client-libraries-usage-csharp

https://cloud.google.com/dotnet/docs/reference/Google.Cloud.PubSub.V1/latest/index

I hope you have found this useful.

Terraform Providers

Rakesh Suryawanshi — Fri, 03 Jun 2022 15:35:00 +0000

This is part-02 of our terraform series, In this one we are discussing terraform providers.

What is Provider?
As per the definition of Provider on Terraform documentation:

Providers are a logical abstraction of an upstream API. They are responsible for understanding API interactions and exposing resources.

What does this means that the providers are responsible for provisioning the resource into cloud platform using the terraform syntax, e.g.: to provision azure resources with terraform you can use azure provider with terraform, I hope this is clear.

Terraform has so many providers built-in for different cloud providers such as aws, azure, google, oracle, cloud-flare etc. these providers are manage and maintain by the cloud team, for e.g. azure provider is manage by azure team, what does it means is if there are any changes introduced by azure on existing azure services or azure introduces new services then azure team will make those updates into azure provider and and release new version, it means that each provider are declared with its own specific version.
The documents and source code link for each provider can be found in terraform website.
Here is the example of terraform azure provider link

https://registry.terraform.io/providers/hashicorp/azurerm/latest

Here you can find the latest version of specific cloud provider.

Terraform Provider declaration

Now let's see: How to declare the terraform provider? In this case we will use the example of azure provider declaration.

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      # terraform with version 3.0.0
      version = "=3.0.0"
    }
  }
}

the argument reference can be found here

registry.terraform.io/providers/hashicorp/azurerm/latest/docs#argument-reference

Here with terraform provider

version - version of terraform provider you can use equal (=) operator for specific version or use >= operator if you want to use version greater then specific version

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = ">=3.0.0"
    }
  }
}

If you want to stick to specific major version with all latest minor release of terraform provider you can do that with "~>" operator as given below, also it is possible to specify multiple provider within a single terraform provider block as given below

terraform {
  required_providers {
    azurerm = {
      # terraform with version 2.88 and all minor release of 2.88
      version = "~> 2.88.1"
      source = "hashicorp/azurerm"
    }
    # terraform azure caf provider
    azurecaf = {
      source = "aztfmod/azurecaf"
    }
  }

  backend "azurerm" {
  }
}

Terraform with feature block

The Azure Provider allows the behaviour of certain resources to be configured using the features block.

This allows different users to select the behaviour they require, for example some users may wish for the OS Disks for a Virtual Machine to be removed automatically when the Virtual Machine is destroyed - whereas other users may wish for these OS Disks to be detached but not deleted.

provider "azurerm" {
  features {
    api_management {
      purge_soft_delete_on_destroy = true
      recover_soft_deleted         = true
    }

    application_insights {
      disable_generated_rule = false
    }

    cognitive_account {
      purge_soft_delete_on_destroy = true
    }

    key_vault {
      purge_soft_delete_on_destroy    = true
      recover_soft_deleted_key_vaults = true
    }

    log_analytics_workspace {
      permanently_delete_on_destroy = true
    }

    resource_group {
      prevent_deletion_if_contains_resources = true
    }

    template_deployment {
      delete_nested_items_during_deletion = true
    }

    virtual_machine {
      delete_os_disk_on_deletion     = true
      graceful_shutdown              = false
      skip_shutdown_and_force_delete = false
    }

    virtual_machine_scale_set {
      force_delete                  = false
      roll_instances_when_required  = true
      scale_to_zero_before_deletion = true
    }
  }
}

Each resource specific block mentioned above is optional, you can specify based on the infrastructure behavior you want for these specifc resources.

How Provider it works?

As I have mentioned in the beginning you need at least one provider block to provision resource with terraform.

When you run terraform initialization command it downloads the terraform provider executable under dot terraform directory (.terraform directory will be created if it doesn't exists), along with terraform modules if you have any modules used in your terraform code.

🦄  terraform init
Initializing modules...

Initializing the backend...

Initializing provider plugins...
- Finding latest version of aztfmod/azurecaf...
- Finding hashicorp/azurerm versions matching "~> 2.88.1"...
- Installing aztfmod/azurecaf v1.2.18...
- Installed aztfmod/azurecaf v1.2.18 (self-signed, key ID 3D457F4D69B172D6)
- Installing hashicorp/azurerm v2.88.1...
- Installed hashicorp/azurerm v2.88.1 (signed by HashiCorp)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Summary

Here is the summary of terraform provider.

You need atleast one provider in your terraform code to provision resources with terraform into your cloud environment.
It's also possible to have multiple provider with your terraform such as local provider, azure provider etc.
It's also possible to write your own custom providers with terraform.

With our discussion above we have discussed about terraform init command with respect to the provider, in our next section we will discuss about terraform commands.

What is terraform?

Rakesh Suryawanshi — Fri, 03 Jun 2022 15:26:00 +0000

In this blog post series we will learn about terraform right from the beginning, this series contains multiple blog post which you can navigate to specific section if you need.

Let's first of all understand

1. What is Infrastructure as Code

Infrastructure as code (IaC) tools allow you to manage infrastructure with configuration files rather than through a graphical user interface. IaC allows you to build, change, and manage your infrastructure in a safe, consistent, and repeatable way by defining resource configurations that you can version, reuse, and share.

2. What is Terraform?
Terraform allows you to manage your infrastructure with code and configuration called HashiCorp's.
It lets you define resources and infrastructure in human-readable, declarative configuration files, and manages your infrastructure's lifecycle. Using Terraform has several advantages over manually managing your infrastructure:

Terraform can manage infrastructure on multiple cloud platforms.
The human-readable configuration language helps you write infrastructure code quickly.
Terraform's state allows you to track resource changes throughout your deployments.
You can commit your configurations to version control to safely collaborate on infrastructure.

3. Install Terraform

Terraform is widely used tool to automate your infrastructure with any cloud provider and its available for Free, you just need to install terraform exe and store in your workstation its really simple.
Terraform installer is version controlled managed by HashiCorp, to download the appropriate version you have to check the terraform documentation.
How to install it ?
There any many ways to install terraform across different operating system (such as Windows, Mac, Linux)

https://learn.hashicorp.com/tutorials/terraform/install-cli

4. Write your first terraform command

Following command can be used to know all the basic commands of terraform

terraform

Main commands:
  init          Prepare your working directory for other commands
  validate      Check whether the configuration is valid
  plan          Show changes required by the current configuration
  apply         Create or update infrastructure
  destroy       Destroy previously-created infrastructure

All other commands:
  console       Try Terraform expressions at an interactive command prompt
  fmt           Reformat your configuration in the standard style
  force-unlock  Release a stuck lock on the current workspace
  get           Install or upgrade remote Terraform modules
  graph         Generate a Graphviz graph of the steps in an operation
  import        Associate existing infrastructure with a Terraform resource
  login         Obtain and save credentials for a remote host
  logout        Remove locally-stored credentials for a remote host
  output        Show output values from your root module
  providers     Show the providers required for this configuration
  refresh       Update the state to match remote systems
  show          Show the current state or a saved plan
  state         Advanced state management
  taint         Mark a resource instance as not fully functional
  test          Experimental support for module integration testing
  untaint       Remove the 'tainted' state from a resource instance
  version       Show the current Terraform version
  workspace     Workspace management

Global options (use these before the subcommand, if any):
  -chdir=DIR    Switch to a different working directory before executing the
                given subcommand.
  -help         Show this help output, or the help for a specified subcommand.
  -version      An alias for the "version" subcommand.

To verify the version of terraform you have installed you can run

terraform version
------------- This should display the output like this -------
Terraform v1.1.2
on windows_amd64
Your version of Terraform is out of date! The latest version
is 1.2.1. You can update by downloading from https://www.terraform.io/downloads.html

5. Integrated Development tool

There are many IDE tools which you have use to start development using terraform, even notepad is okay, the most widely used IDE right now is Visual Studio Code, which you can download for free.
With VSCode there are many extensions you can install which can ease you terraform development experience.
following of them I have installed in my VSCode

Run Logic App workflow using postman

Rakesh Suryawanshi — Thu, 05 May 2022 14:47:08 +0000

In our previous blogpost I have shared How Get Logic App workflow details using postman in this blog I am going share a simple code which you can use to trigger logic app workflow from postman or REST API.

In our last blog we have created postman collection we are going to use the same here and add new request to the collection

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{logicAppName}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/{action}?api-version=2018-11-01

Here in this case:

subscriptionId : Azure subscription Id
resourceGroupName : name of the resource group in which logic app is created.
logicAppName: logic app name.
workflow name: logic app workflow name, one logic app can have multiple workflow
triggerName: name of the trigger type of your logic app workflow (e.g.: Recurrence)
action: run

trigger name for the workflow you can find on the dashboard of the logic app

Once you have all this information you can simply trigger the logic app workflow from postman.

Here is the result:

That's it really, this a simple example of how to use postman to run the logic app workflow.

In the next blog I will discuss how to use specflow for testing logic app, till then please follow me here on dev.to.

You can also follow me on medium blog!!

I also have my YouTube channel please subscribe!! to my channel there.

Get Logic App Workflow using REST API (Postman)

Rakesh Suryawanshi — Thu, 05 May 2022 14:14:46 +0000

In this article I am sharing how to get logic app workflow details using azure management REST API from postman?

Logic app are serverless offering from Microsoft, it has been evolved a lot in last period or so and its keep on changing, now the logic app service is part of AppService and you need to provision the logic app inside the App service plan... this information might not sound relevant to this blog but it does actually, Microsoft has the rich set of REST API documentation for all different azure services (including logic apps) which we can use to get REST endpoint outcome from these API, incase of logic app RESTAPI the endpoint as of date (May, 04 2022) its still pointing to the standalone workflow instead of logic app being AppService resource type.

Logic App REST API Doc

It means that document say to get the workflow details of logic you need to call logic app endpoint
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}?api-version=2016-06-01

but unfortunately this does not return the output.

Instead of this you need to call following REST API URL:

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{logicapp-name}/workflows/{workflowName}?api-version=2022-03-01



https://management.azure.com//subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{logicapp-name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}?api-version=2018-11-01

This a change which Microsoft should make into REST API and I hope they will update the documents very soon, may be it's already update by the time you are reading this blog.

Create Postman collection

Now lets see how to get workflow details using Postman.

In the postman I have create a collection, that collection first of all we need to write pre-request script to create workflow, here the script code which you can use.



pm.sendRequest({
    url: 'https://login.microsoftonline.com/' + pm.collectionVariables.get("TenantID") + '/oauth2/token',
    method: 'POST',
    header: {
        'Content-Type': 'application/x-www-form-urlencoded'
    },
    body: {
        mode: 'urlencoded',
          urlencoded: [
            {key: "grant_type", value: "client_credentials"},
            {key: "client_id", value: pm.collectionVariables.get("ClientID")},
            {key: "client_secret", value: pm.collectionVariables.get("ClientSecret")},
            {key: "resource", value: pm.collectionVariables.get("Resource")}
          ]
    }
}, function (err, res) {
    pm.collectionVariables.set("Token", res.json().access_token);
});

we also need service principal to create bearer token and the details of service principal and azure subscription is capture into postman collection variable.

Create Postman request

in our collection we will add new service request and add get request



https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}?api-version=2016-06-01

Setup authorization for your request and use bearer token variable here

Once you replace the variable as per your logic app details you are ready to run.

The output will contains everything about your logic including workflow definition in json format.

That's it really, this a simple example of how to use postman to get the logic app workflow.

In the next blog I will discuss how to trigger logic app workflow from postman, till then please follow me here on dev.to.

You can also follow me on medium blog!!

I also have my YouTube channel please subscribe!! to my channel there.