Skip to content

[Initiative] Namespaces #39

@juliuskrah

Description

@juliuskrah

Summary

Introduce namespaces to allow multiple teams, organisations, or enterprises to manage their own git repositories of catalogs and configs within the same platform without conflicts. #100 and #65 provides the foundations for this task.

Scope

In scope:

  • Namespace isolation for repositories containing catalogs and configurations
  • Namespace-scoped access control
  • Userspace, organisation, and enterprise tiers

Out of scope:

  • Cross-namespace sharing/federation (future)

Acceptance Criteria

  • Repositories are fully isolated between namespaces
  • Access control is enforced at the namespace boundary
  • All three tiers (user/org/enterprise) are supported (think GitHub namespaces)
  • Namespace creation and deletion are auditable

Tracking

  • Milestone: TBD
  • Labels: area/auth, priority/p2

Subtasks

Metadata

Metadata

Assignees

No one assigned
    No fields configured for Feature.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions