mirror of
https://github.com/harness/drone.git
synced 2025-05-04 15:19:26 +08:00
3ba0f75c8d
This change adds the following:
- Space UID + Custom harness validation (accountId for top level space, harness identifier for child spaces)
- Repo UID + Custom harness validation (harness identifier)
- Store Unique casing of space / repo path and add Path.ValueUnique (with Unique index) to allow for application layer controlling the case sensitivity (case insensitive standalone vs partially case sensitive harness)
- Token UID (unique index over ownertype + ownerID + tokenUID)
- Add DisplayName for principals (replaces Name to avoid confustion)
- Store Unique casing of principal UID and add Principal.ValueUnique (with unique index) to allow for application layer, per principal type control of case sensitivity (required in embedded mode)
- Generate serviceAccount UID (+Email) Randomly (sa-{space|repo}-{ID}-{random}) - Allows to have a unique UID across all principals while reducing likelyhood of overlaps with users + avoid overlap across spaces / repos.
- Sync casing of space names (accountId orgId projectId) when creating spaces on the fly (to ensure case sensitivity of - harness code) or use the existing space to update casing.
- Update serviceaccount client to match updated NG Manager API
- in embedded mode create spaces for harness resources owning the service account
44 lines
1.7 KiB
Go
44 lines
1.7 KiB
Go
// Copyright 2022 Harness Inc. All rights reserved.
|
|
// Use of this source code is governed by the Polyform Free Trial License
|
|
// that can be found in the LICENSE.md file for this repository.
|
|
|
|
package types
|
|
|
|
import (
|
|
"github.com/harness/gitness/types/enum"
|
|
)
|
|
|
|
/*
|
|
Space represents a space.
|
|
There isn't a one-solves-all hierarchical data structure for DBs,
|
|
so for now we are using a mix of materialized paths and adjacency list.
|
|
Every space stores its parent, and a space's path is stored in a separate table.
|
|
PRO: Quick lookup of childs, quick lookup based on fqdn (apis)
|
|
CON: Changing a space uid requires changing all its ancestors' Paths.
|
|
|
|
Interesting reads:
|
|
https://stackoverflow.com/questions/4048151/what-are-the-options-for-storing-hierarchical-data-in-a-relational-database
|
|
https://www.slideshare.net/billkarwin/models-for-hierarchical-data
|
|
*/
|
|
type Space struct {
|
|
// TODO: int64 ID doesn't match DB
|
|
ID int64 `db:"space_id" json:"id"`
|
|
ParentID int64 `db:"space_parentId" json:"parentId"`
|
|
Path string `db:"space_path" json:"path"`
|
|
UID string `db:"space_uid" json:"uid"`
|
|
Description string `db:"space_description" json:"description"`
|
|
IsPublic bool `db:"space_isPublic" json:"isPublic"`
|
|
CreatedBy int64 `db:"space_createdBy" json:"createdBy"`
|
|
Created int64 `db:"space_created" json:"created"`
|
|
Updated int64 `db:"space_updated" json:"updated"`
|
|
}
|
|
|
|
// Stores spaces query parameters.
|
|
type SpaceFilter struct {
|
|
Page int `json:"page"`
|
|
Size int `json:"size"`
|
|
Query string `json:"query"`
|
|
Sort enum.SpaceAttr `json:"sort"`
|
|
Order enum.Order `json:"direction"`
|
|
}
|