Skip to content

[Feature Request]: Align CosmosDB deployment validation to other modules #2231

@eriqua

Description

@eriqua

Description

Related to issue #1564
Discussion started in PR #1993

Cosmos DB has 4 tests:

  • 1 for a plain resource, where only the parent resource type is deployed together with diagnostic settings, locks and rbac
  • 3 additional tests, testing each a different child resource: mongodb, gremlindb and sqldb

This seems a bit inconsistent with the majority of the other modules. The most consistent approach would be to have:

  • a min test: similar to plain, but removing diagnostics, locks and rbac, hence testing only required parameters
  • a common test: deploying gremlindb, sqldb and mongodb child resources together with additional features like locks, diagnostics and rbac.

    Note: That however depends on if the CosmosDB service allowes multiple types deployed at once

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions