Using Locally with the Pulumi Azure Classic Provider

Creating a Pulumi Project

Pulumi doesn't ship a first-party template for the Azure Classic provider, so we'll start from the empty Go template and bring in the Classic SDK ourselves. In an empty directory, run:

Following the built-in prompts gives us a scaffolded Pulumi project with an empty main.go. Replace its contents with the Resource Group example from the locallybuild/examples repository:

package main

import (
  "github.com/pulumi/pulumi-azure/sdk/v6/go/azure/core"
  "github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
  pulumi.Run(func(ctx *pulumi.Context) error {
    _, err := core.NewResourceGroup(ctx, "pulumi-resourcegroup", &core.ResourceGroupArgs{
      Location: pulumi.StringPtr("berlin"),
    })
    if err != nil {
      return err
    }

    return nil
  })
}

Then pull in the Azure Classic SDK:

Provisioning a Resource Group

At this point we're ready to provision our infrastructure. If you haven't already started Locally, you can do so using:

Since the Pulumi project that we've created sources credentials from the Environment (that is, using Environment Variables) - we can use Automatic Configuration to run this against Locally:

When we do, Pulumi will download the required dependencies, provision the infrastructure and then output the result.

With Pulumi having finished provisioning, if we open the First Subscription within the Locally Dashboard, and view the Resource Groups then we should see our newly created Resource Group.

Whilst this example shows how to use the Pulumi Golang SDK to provision a Resource Group, as Pulumi supports different providers and languages for interacting with Azure, you should be able to use Locally with any of them. Just be sure you're using the most recent version of the provider.

Next steps

You can find more examples of how to use Pulumi with Locally in the Examples in the Documentation. To run pulumi up against Locally in your pipeline, see Using Locally in CI.

Should you encounter any issues, please take a look at the troubleshooting section.