Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Gremlin Database and Gremlin Graph within Azure CosmosDB #4970

Closed
materia-org opened this issue Nov 25, 2019 · 4 comments
Closed
Labels
new-resource service/cosmosdb upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Milestone

Comments

@materia-org
Copy link

materia-org commented Nov 25, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Terraform already ships with resources to access Azure CosmosDB's MongoDB, CassandraDB and Table API. However, analogous resources for GremlinDB are still missing. This should be quick to acheive.

Proposed Resource(s)

  1. azurerm_cosmosdb_gremlin_database
  2. azurerm_cosmosdb_gremlin_graph

Potential Terraform Configuration

  1. Example main.tf for azurerm_cosmosdb_gremlin_database:
resource "azurerm_cosmosdb_gremlin_database" "main" {
  name                = var.gremlindbName
  resource_group_name = var.argMainName
  account_name        = var.cosmosdbName
}
  1. Example main.tf for azurerm_cosmosdb_gremlin_graph:
resource "azurerm_cosmosdb_gremlin_graph" "main" {
  name                = var.gremlindbName
  resource_group_name = var.argMainName
  account_name        = var.cosmosdbName
  graph_name          = var.graphName

  indexing_policy {
    indexing_mode  = "consistent"
    automatic      = true
    included_paths = [{ path = "/*" }]
    excluded_paths = [{ path = "/\"_etag\"/?" }]
  }

  conflict_resolution_policy {
    mode                     = "LastWriterWins"
    conflict_resolution_path = "/_ts"
  }
}

resource "azurerm_cosmosdb_gremlin_graph_throughout" "main" {
  name                = var.gremlindbName
  resource_group_name = var.argMainName
  account_name        = var.cosmosdbName
  graph_name          = var.graphName
  throughput          = 10000
}

References

https://docs.microsoft.com/en-us/azure/cosmos-db/graph-introduction
https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-gremlin-console

  • #0000
@SebRosander
Copy link
Contributor

I've started to look into azurerm_cosmosdb_gremlin_graph parts as well. Still a newbie in go and haven't worked with gremlin that much, so it may take some time. Bear with me.

katbyte pushed a commit that referenced this issue Jan 8, 2020
@katbyte katbyte added this to the v1.41.0 milestone Jan 8, 2020
@katbyte
Copy link
Collaborator

katbyte commented Jan 8, 2020

fixed by #5301

@katbyte katbyte closed this as completed Jan 8, 2020
@ghost
Copy link

ghost commented Jan 16, 2020

This has been released in version 1.41.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.41.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Feb 8, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Feb 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-resource service/cosmosdb upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Projects
None yet
Development

No branches or pull requests

5 participants