You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, cnquery only supports listing Cosmos DB accounts of the NoSQL type. We request the inclusion of support for additional Cosmos DB types such as MongoDB, Cassandra, Gremlin, Table, and PostgreSQL.
Context:
Azure Cosmos DB offers various APIs to serve to different use cases, as shown below:
Azure Cosmos DB for NoSQL
Azure Cosmos DB for MongoDB
Azure Cosmos DB for Apache Cassandra
Azure Cosmos DB for Apache Gremlin
Azure Cosmos DB for Table
Azure Cosmos DB for PostgreSQL
Currently, the cnquery integration only lists Cosmos DB accounts of the NoSQL type, which limits visibility and management of other types of Cosmos DB resources.
Proposed Solution:
Enhance the existing Cosmos DB support (cosmosdb.go in azure) to include querying and listing for all the above-mentioned types. This will involve:
Creating Clients for Different Resource Types: Add clients for MongoDB clusters, Cassandra clusters, Gremlin clusters, Table clusters, and PostgreSQL clusters.
Query Each Resource Type: Modify the code to query each type and aggregate the results.
The text was updated successfully, but these errors were encountered:
Issue Description:
Currently, cnquery only supports listing Cosmos DB accounts of the NoSQL type. We request the inclusion of support for additional Cosmos DB types such as MongoDB, Cassandra, Gremlin, Table, and PostgreSQL.
Context:
Azure Cosmos DB offers various APIs to serve to different use cases, as shown below:
Currently, the cnquery integration only lists Cosmos DB accounts of the NoSQL type, which limits visibility and management of other types of Cosmos DB resources.
Proposed Solution:
Enhance the existing Cosmos DB support (cosmosdb.go in azure) to include querying and listing for all the above-mentioned types. This will involve:
The text was updated successfully, but these errors were encountered: