Top / Microsoft Azure / Azure CosmosDB (DocumentDB) / Gremlin Graph

Azure CosmosDB (DocumentDB) Gremlin Graph

This page shows how to write Terraform and Azure Resource Manager for CosmosDB (DocumentDB) Gremlin Graph and write them securely.

terraform-logo

Review your .tf file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

azurerm_cosmosdb_gremlin_graph (Terraform)

The Gremlin Graph in CosmosDB (DocumentDB) can be configured in Terraform with the resource name azurerm_cosmosdb_gremlin_graph. The following sections describe 10 examples of how to use the resource and its parameters.

Example Usage from GitHub

cosmosdb_gremlin_graph_test.tf#L90
resource "azurerm_cosmosdb_gremlin_graph" "serverless" {
  name                = "tfex-cosmos-gremlin-graph"
  resource_group_name = azurerm_cosmosdb_account.example.resource_group_name
  account_name        = azurerm_cosmosdb_account.example.name
  database_name       = azurerm_cosmosdb_gremlin_database.example.name
  partition_key_path  = "/Example"
cosmosdb_gremlin_graph_test.tf#L90
resource "azurerm_cosmosdb_gremlin_graph" "serverless" {
  name                = "tfex-cosmos-gremlin-graph"
  resource_group_name = azurerm_cosmosdb_account.example.resource_group_name
  account_name        = azurerm_cosmosdb_account.example.name
  database_name       = azurerm_cosmosdb_gremlin_database.example.name
  partition_key_path  = "/Example"
gremlin_graph.tf#L4
resource "azurerm_cosmosdb_gremlin_graph" "graph" {
  name                = var.settings.name
  resource_group_name = var.resource_group_name
  account_name        = var.cosmosdb_account_name
  database_name       = var.gremlin_database_name
  partition_key_path  = var.settings.partition_key_path
gremlin_graph.tf#L4
resource "azurerm_cosmosdb_gremlin_graph" "graph" {
  name                = var.settings.name
  resource_group_name = var.resource_group_name
  account_name        = var.cosmosdb_account_name
  database_name       = var.gremlin_database_name
  partition_key_path  = var.settings.partition_key_path
gremlin_graph.tf#L4
resource "azurerm_cosmosdb_gremlin_graph" "graph" {
  name                = var.settings.name
  resource_group_name = var.resource_group_name
  account_name        = var.cosmosdb_account_name
  database_name       = var.gremlin_database_name
  partition_key_path  = var.settings.partition_key_path
gremlin_graph.tf#L4
resource "azurerm_cosmosdb_gremlin_graph" "graph" {
  name                = var.settings.name
  resource_group_name = var.resource_group_name
  account_name        = var.cosmosdb_account_name
  database_name       = var.gremlin_database_name
  partition_key_path  = var.settings.partition_key_path
main.tf#L7
resource "azurerm_cosmosdb_gremlin_graph" "this" {
  account_name        = var.account_name
  database_name       = var.database_name
  name                = var.name
  partition_key_path  = var.partition_key_path
  resource_group_name = var.resource_group_name
cosmosdb.tf#L33
resource "azurerm_cosmosdb_gremlin_graph" "skillsmatrix" {
  name                = "skills-matrix-graph"
  resource_group_name = azurerm_cosmosdb_account.skillsmatrix.resource_group_name
  account_name        = azurerm_cosmosdb_account.skillsmatrix.name
  database_name       = azurerm_cosmosdb_gremlin_database.skillsmatrix.name
  partition_key_path  = "/Company"
gremlin_graph.tf#L4
resource "azurerm_cosmosdb_gremlin_graph" "graph" {
  name                = var.settings.name
  resource_group_name = var.resource_group_name
  account_name        = var.cosmosdb_account_name
  database_name       = var.gremlin_database_name
  partition_key_path  = var.settings.partition_key_path
main.tf#L7
resource "azurerm_cosmosdb_gremlin_graph" "this" {
  account_name        = var.account_name
  database_name       = var.database_name
  name                = var.name
  partition_key_path  = var.partition_key_path
  resource_group_name = var.resource_group_name

Review your Terraform file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

>> from Terraform Registry

Explanation in Terraform Registry

Manages a Gremlin Graph within a Cosmos DB Account.

>> from Terraform Registry

Microsoft.DocumentDB/databaseAccounts/gremlinDatabases/graphs (Azure Resource Manager)

The databaseAccounts/gremlinDatabases/graphs in Microsoft.DocumentDB can be configured in Azure Resource Manager with the resource name Microsoft.DocumentDB/databaseAccounts/gremlinDatabases/graphs. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Parameters

  • apiVersion required - string
  • location optional - string

    The location of the resource group to which the resource belongs.

  • name required - string

    Cosmos DB graph name.

  • properties required
      • options optional
          • autoscaleSettings optional
              • maxThroughput optional - integer

                Represents maximum throughput, the resource can scale up to.

          • throughput optional - integer

            Request Units per second. For example, "throughput": 10000.

      • resource required
          • conflictResolutionPolicy optional
              • conflictResolutionPath optional - string

                The conflict resolution path in the case of LastWriterWins mode.

              • conflictResolutionProcedure optional - string

                The procedure to resolve conflicts in the case of custom mode.

              • mode optional - string

                Indicates the conflict resolution mode.

          • defaultTtl optional - integer

            Default time to live

          • id required - string

            Name of the Cosmos DB Gremlin graph

          • indexingPolicy optional
              • automatic optional - boolean

                Indicates if the indexing policy is automatic

              • compositeIndexes optional - array

                List of composite path list

              • excludedPaths optional array
                  • path optional - string

                    The path for which the indexing behavior applies to. Index paths typically start with root and end with wildcard (/path/*)

              • includedPaths optional array
                  • indexes optional array
                      • dataType optional - string

                        The datatype for which the indexing behavior is applied to.

                      • kind optional - string

                        Indicates the type of index.

                      • precision optional - integer

                        The precision of the index. -1 is maximum precision.

                  • path optional - string

                    The path for which the indexing behavior applies to. Index paths typically start with root and end with wildcard (/path/*)

              • indexingMode optional - string

                Indicates the indexing mode.

              • spatialIndexes optional array
                  • path optional - string

                    The path for which the indexing behavior applies to. Index paths typically start with root and end with wildcard (/path/*)

                  • types optional - array

                    List of path's spatial type

          • partitionKey optional
              • kind optional - string

                Indicates the kind of algorithm used for partitioning. For MultiHash, multiple partition keys (upto three maximum) are supported for container create.

              • paths optional - array

                List of paths using which data within the container can be partitioned

              • version optional - integer

                Indicates the version of the partition key definition

          • uniqueKeyPolicy optional
              • uniqueKeys optional array
                  • paths optional - array

                    List of paths must be unique for each document in the Azure Cosmos DB service

  • tags optional - string

    Tags are a list of key-value pairs that describe the resource. These tags can be used in viewing and grouping this resource (across resource groups). A maximum of 15 tags can be provided for a resource. Each tag must have a key no greater than 128 characters and value no greater than 256 characters. For example, the default experience for a template type is set with "defaultExperience": "Cassandra". Current "defaultExperience" values also include "Table", "Graph", "DocumentDB", and "MongoDB".

  • type required - string

>> from Azure Resource Manager Documentation

The Other Related Azure CosmosDB (DocumentDB) Resources

Frequently asked questions

What is Azure CosmosDB (DocumentDB) Gremlin Graph?

Azure CosmosDB (DocumentDB) Gremlin Graph is a resource for CosmosDB (DocumentDB) of Microsoft Azure. Settings can be wrote in Terraform.

Where can I find the example code for the Azure CosmosDB (DocumentDB) Gremlin Graph?

For Terraform, the gilyas/infracost, infracost/infracost and anmoltoppo/Terraform source code examples are useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.

Table of Contents