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

DocumentDB only provisions a Microsoft.DocumentDB/databaseAccounts #259

Closed
jeremyrickard opened this issue Feb 12, 2018 · 1 comment
Closed
Assignees

Comments

@jeremyrickard
Copy link
Contributor

@jeremyrickard jeremyrickard commented Feb 12, 2018

The current DocumentDB service only provisions a Microsoft.DocumentDB/databaseAccounts. I think we should apply the same sort of pattern that we are doing with MySQL, PostgreSQL and SQLDB to this one. We probably also need to include whatever the generated database name is in the binding when we create it so you can reliably connect to it. The Java SDK from the Azure Java team requires the URI (which can point to an instance with N databases), the key and the database name you want to use. The current experience kind of requires a step outside the broker to really make DocumentDB usable, either the app needs to know what it wants to go create or you need to create it manually via the portal or API.

It doesn't appear that this can be done via ARM, so we might need to do a hybrid approach of ARM + API calls via the go sdk.

@krancour krancour self-assigned this Mar 6, 2018
@krancour krancour added this to the v0.10.0-alpha milestone Mar 6, 2018
@krancour krancour assigned jeremyrickard and unassigned krancour Mar 6, 2018
@jeremyrickard jeremyrickard removed this from the v0.10.0-alpha milestone Mar 26, 2018
@jeremyrickard

This comment has been minimized.

Copy link
Contributor Author

@jeremyrickard jeremyrickard commented Mar 26, 2018

Removed from the v0.10.0 milestone since we want to discuss this more before we decide if it's a thing we'll do.

jeremyrickard pushed a commit to jeremyrickard/open-service-broker-azure that referenced this issue Apr 25, 2018
Jeremy Rickard
This PR introduces the needed logic and changes to allow the user to provision
the equivalent of an All-In-One CosmosDB instance: a database account and
a database. This is functionally equivalent to what MASB did, but follows
the OSBA pattern of not allowing the user to name things.

Closes: Azure#259
jeremyrickard pushed a commit to jeremyrickard/open-service-broker-azure that referenced this issue Apr 26, 2018
This PR introduces the needed logic and changes to allow the user to provision
the equivalent of an All-In-One CosmosDB instance: a database account and
a database. This is functionally equivalent to what MASB did, but follows
the OSBA pattern of not allowing the user to name things.

Closes: Azure#259
krancour added a commit that referenced this issue Apr 30, 2018
* WIP all in one

* Adding ability to provision ComosDB SQL API database

This PR introduces the needed logic and changes to allow the user to provision
the equivalent of an All-In-One CosmosDB instance: a database account and
a database. This is functionally equivalent to what MASB did, but follows
the OSBA pattern of not allowing the user to name things.

Closes: #259

* Lint fixes

* Cleanup

* Lint fix

* Update cosmosdb_cases_test.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.