Product Roadmap - TimCsaky/common-object-management-service GitHub Wiki

Below is a rough outline of the features that we are targeting for COMS.

v0.1.0 - Minimum Viable Product (MVP)

General

  • General Documentation
  • Database action auditing
  • Over 50% coverage in unit tests

Authentication

  • Multiple authentication modes
    • Unauthenticated
    • Basic
    • OIDC
    • Full (Basic and OIDC)
  • Support multiple identity providers (eg: IDIR, BCeID)

Object Operations

  • Upload multiple objects to storage
  • Expiring object download links
  • Object versioning and history

Permission Management

  • Share objects
  • Search for OIDC users
  • Toggle object for public access
  • Update and manage object permissions

v0.2.0 - Version Tracking

  • Explicit version management
  • Soft-delete objects
  • Enhance validation layer support

v0.3.0 - Metadata & Tagging

  • Object metadata
  • Object tagging
  • Object discovery via metadata/tagging

v0.4.0 - Multi-tenant Bucket support

  • Multi-bucket support
  • Database refactor
  • Permission cascade/inheritance refactor
  • API shape extensions

v0.4.1 - Reliability Pass

  • Improve architectural documentation
  • Refactor objection model mock pattern; improve unit test coverage
  • Validate bucket credentials on add and allow folder key to be optional
  • Performance improvements

v0.4.2 - Domain Scoped Metadata Keys

  • Change mandatory metadata keys to be domain scoped

v0.5.0 - Filename Support

  • Support arbitrary filenames for S3 Objects
  • Add First Nations glyph support to filenames
  • Track and enforce coms-id as an S3 tag
  • Deprecate coms-id and coms-name S3 metadata enforcement
  • Add tracking support for version-specific S3 ETags

v0.6.0 - Synchronization

  • Add global synchronization support for coms-id tags
  • Add proactive coms-id tag annotation support for objects
  • Add user-defined probe for S3 Bucket endpoint
  • Add retroactive backfill for existing S3 buckets and directories
  • Retroactive bucket/database population
  • Cron-job considerations for periodic synchronization
  • Potential merge-conflict logic for data collision scenarios

v0.7.0 - TBD

  • ???