Azure / Azure/azure-rest-api-specs

CosmosDB: missing endpoint entries for Azure Table, Cassandra and Gremlin

Open
#3,107 2 comments 0 reactions 0 assignees View on GitHub
Cosmos Doc Db feature-request Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

When creating an Azure Table, Cassandra or Gremlin Cosmos DB accounts, the service returns an additional endpoint that is specific to the selected "capability". The current Swagger spec do not capture these endpoints while the Azure Portal does. Can we add them please?

![screen shot 2018-05-18 at 3 37 00 pm](https://user-images.githubusercontent.com/15163996/40261890-377c2782-5ab8-11e8-8a8b-4e62139a747a.png)

Contributor guide

Open the contributing guide

Research direction

Locate the Cosmos DB API specification in the repository and compare its account endpoint definitions with the Azure Portal behavior described in the issue. Check the capability-specific endpoints for Azure Table, Cassandra, and Gremlin, then verify that the updated specification represents all three endpoint entries consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, cassandra, openapi
Domain
api, cloud, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.