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 DatabaseAccountGetResults capability is not returning all types of capabilities #12229

Closed
sburnwal opened this issue Aug 14, 2020 · 5 comments
Assignees
Labels
Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@sburnwal
Copy link

Bug Report

  • import path of package in question "github.com/Azure/azure-sdk-for-go/services/cosmos-db/mgmt/2019-12-12/documentdb"

  • SDK version 39.1

    • Specify the exact commit if possible; one way to get this is the REVISION
      column output by dep status "github.com/Azure/azure-sdk-for-go.
  • output of go version
    go version go1.11 linux/amd64

  • What happened?
    Not able to get all the EnabledApiTypes that are returned by REST API when querying cosmos account DatabaseAccountGetResults

  • What did you expect or want to happen?
    Cosmos account can have multiple EnabledApiTypes. For example when I create Cosmos account of type Gremlin, it has EnabledApiTypes = Gremlin, Sql. But when use the GO SDK to query it, Capabilities returns only Gremlin. So is the case with Cosmos account of type Azure table

  • How can we reproduce it?
    Create Cosmos account with type Gremlin.

  • Anything we should know about your environment.
    No

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 14, 2020
@ArcturusZhang ArcturusZhang added Cosmos Service Attention Workflow: This issue is responsible by Azure service team. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 14, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 14, 2020
@ghost
Copy link

ghost commented Aug 14, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @wmengmsft, @MehaKaushik, @shurd, @anfeldma-ms.

@MehaKaushik
Copy link

Hey @sburnwal Capabilities indicates the current account's capabilities. The account in picture is a Gremlin account, hence its capabilities would include EnableGremlin. EnabledApiTypes is not a supported param for REST API for CosmosDB ResourceProvider. (Please note Resource Provider operations are Control Plane operations.)
Our REST API are described here https://docs.microsoft.com/en-us/rest/api/cosmos-db-resource-provider/databaseaccounts

Please let me know if this helps and if you have any more queries.

@sburnwal
Copy link
Author

sburnwal commented Aug 14, 2020

When I create Private Endpoint for a Gremlin Cosmos account, it is asking me to choose 'Gremlin' or 'Sql' as the sub resource. From the Go SDK I do get the 'EnableGremlin' as the capability. Which API will also give me the other sub resource type 'Sql' ? So that I can create a private endpoint of Sql type ?

@MehaKaushik
Copy link

MehaKaushik commented Sep 8, 2020

Apologies for my delayed response. Sql is the default API, so you dont need to set any capability for it.

@MehaKaushik
Copy link

Hey @sburnwal I hope your questions were answered. I am closing this issue, please re-open this if you have more queries.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants