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

Cosmos DB - database and collection resources #252

Closed
mikhailshilkov opened this issue May 17, 2019 · 4 comments
Closed

Cosmos DB - database and collection resources #252

mikhailshilkov opened this issue May 17, 2019 · 4 comments
Assignees
Labels
area/providers kind/enhancement Improvements or new features

Comments

@mikhailshilkov
Copy link
Member

Currently, Pulumi only supports creating Cosmos DB accounts - not databases or collections.

Terraform just merged this support, so I'm creating this issue to make sure we transfer this capability to Pulumi.

In addition, we need to add/update an example and enable serverless trigger on the collection resource level.

@mikhailshilkov
Copy link
Member Author

Ok, the databases are supported now, but not SQL Collections yet.

@mikhailshilkov mikhailshilkov self-assigned this May 20, 2019
@stack72
Copy link
Contributor

stack72 commented Jun 3, 2019

@mikhailshilkov can you give me a quick TL;DR of what is still required for this issue? Is this a limitation upstream?

@mikhailshilkov
Copy link
Member Author

Yes, they added a database and some collection types, but not the "SQL Collection" - a native Cosmos DB collection, see hashicorp/terraform-provider-azurerm#3506

@stack72 stack72 added area/providers kind/enhancement Improvements or new features labels Jun 4, 2019
@stack72
Copy link
Contributor

stack72 commented Jun 4, 2019

@mikhailshilkov, as this is a missing resource upstream, I am going to close this out as a duplicate of upstream. When the work to add support for SQL Collections is added, we will get a warning in the code generation that we need to add it

I am going to link hashicorp/terraform-provider-azurerm#3506 as the correct place for the questions on this

@stack72 stack72 closed this as completed Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants