The native Azure Pulumi provider exposes the entire resource model of Azure Resource Manager. Each resource can be created, updated, deleted, or refreshed (read).
However, Azure API has many endpoints that don't map to our resource model. For examples, finding resources given some filter criteria is not supported directly.
You can easily integrate an Azure SDK call or a raw HTTP request inside your Pulumi program using the same programming language. We provide a helper function Authorization.GetClientToken()
that returns a valid authentication token for the same login context that the Pulumi provider is using.
This example demonstrates how to use such integration to lookup a role definition ID based on its name and scope. It then creates a role assignment for the resulting definition to allow pulling container images from a registry.
-
Create a new stack:
$ pulumi stack init dev
-
Login to Azure CLI (you will be prompted to do this during deployment if you forget this step):
$ az login
-
Set the Azure region location to use:
$ pulumi config set azure-native:location westus2
-
Run
pulumi up
to preview and deploy changes:$ pulumi up Previewing changes: ... Performing changes: ... Resources: ~ 1 updated 3 unchanged