Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • I infra-azure-provisioning
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Deployment and Operations
  • infra-azure-provisioning
  • Issues
  • #91
Closed
Open
Issue created Jan 18, 2021 by Aalekh Jain@aalekhjMaintainer

Support for assigning unique keys in cosmos collections

Why is this needed

Unique key constraints in Azure Cosmos DB make sure that one or more values within a logical partition is unique.

Current behaviour

Currently there is no support for adding unique keys for a cosmos collection during deployment.

Expected behavior

Adding support for unique keys will allow us to set the unique keys required for the cosmos collection(s). For the collection WorkflowTasksSharingInfo used by ingestion service, we need to make sure that runId is a unique key, for which support needs to be added.

Acceptance criteria

  • Add functionality to assign unique keys for cosmos collection
  • Obtain approval for any infrastructure requirements.
  • Implement any required infrastructure changes.
  • Obtain approval for merge request(s) containing infrastructure changes.

Note: Upon adding the support for unique keys, this will bring in a breaking change as the cosmos collection WorkflowTasksSharingInfo will be deleted and re-created. This will be raised in a separate MR.

Edited Jan 18, 2021 by Aalekh Jain
Assignee
Assign to
Time tracking