mirror of
https://github.com/coder/coder.git
synced 2025-07-03 16:13:58 +00:00
4c33846f6d
Pre-requisite for https://github.com/coder/coder/pull/16891 Closes https://github.com/coder/internal/issues/515 This PR introduces a new concept of a "system" user. Our data model requires that all workspaces have an owner (a `users` relation), and prebuilds is a feature that will spin up workspaces to be claimed later by actual users - and thus needs to own the workspaces in the interim. Naturally, introducing a change like this touches a few aspects around the codebase and we've taken the approach _default hidden_ here; in other words, queries for users will by default _exclude_ all system users, but there is a flag to ensure they can be displayed. This keeps the changeset relatively small. This user has minimal permissions (it's equivalent to a `member` since it has no roles). It will be associated with the default org in the initial migration, and thereafter we'll need to somehow ensure its membership aligns with templates (which are org-scoped) for which it'll need to provision prebuilds; that's a solution we'll have in a subsequent PR. --------- Signed-off-by: Danny Kopping <dannykopping@gmail.com> Co-authored-by: Sas Swart <sas.swart.cdk@gmail.com>
58 lines
2.4 KiB
SQL
58 lines
2.4 KiB
SQL
ALTER TABLE users
|
|
ADD COLUMN is_system bool DEFAULT false NOT NULL;
|
|
|
|
COMMENT ON COLUMN users.is_system IS 'Determines if a user is a system user, and therefore cannot login or perform normal actions';
|
|
|
|
INSERT INTO users (id, email, username, name, created_at, updated_at, status, rbac_roles, hashed_password, is_system, login_type)
|
|
VALUES ('c42fdf75-3097-471c-8c33-fb52454d81c0', 'prebuilds@system', 'prebuilds', 'Prebuilds Owner', now(), now(),
|
|
'active', '{}', 'none', true, 'none'::login_type);
|
|
|
|
DROP VIEW IF EXISTS group_members_expanded;
|
|
CREATE VIEW group_members_expanded AS
|
|
WITH all_members AS (
|
|
SELECT group_members.user_id,
|
|
group_members.group_id
|
|
FROM group_members
|
|
UNION
|
|
SELECT organization_members.user_id,
|
|
organization_members.organization_id AS group_id
|
|
FROM organization_members
|
|
)
|
|
SELECT users.id AS user_id,
|
|
users.email AS user_email,
|
|
users.username AS user_username,
|
|
users.hashed_password AS user_hashed_password,
|
|
users.created_at AS user_created_at,
|
|
users.updated_at AS user_updated_at,
|
|
users.status AS user_status,
|
|
users.rbac_roles AS user_rbac_roles,
|
|
users.login_type AS user_login_type,
|
|
users.avatar_url AS user_avatar_url,
|
|
users.deleted AS user_deleted,
|
|
users.last_seen_at AS user_last_seen_at,
|
|
users.quiet_hours_schedule AS user_quiet_hours_schedule,
|
|
users.name AS user_name,
|
|
users.github_com_user_id AS user_github_com_user_id,
|
|
users.is_system AS user_is_system,
|
|
groups.organization_id,
|
|
groups.name AS group_name,
|
|
all_members.group_id
|
|
FROM ((all_members
|
|
JOIN users ON ((users.id = all_members.user_id)))
|
|
JOIN groups ON ((groups.id = all_members.group_id)))
|
|
WHERE (users.deleted = false);
|
|
|
|
COMMENT ON VIEW group_members_expanded IS 'Joins group members with user information, organization ID, group name. Includes both regular group members and organization members (as part of the "Everyone" group).';
|
|
-- TODO: do we *want* to use the default org here? how do we handle multi-org?
|
|
WITH default_org AS (SELECT id
|
|
FROM organizations
|
|
WHERE is_default = true
|
|
LIMIT 1)
|
|
INSERT
|
|
INTO organization_members (organization_id, user_id, created_at, updated_at)
|
|
SELECT default_org.id,
|
|
'c42fdf75-3097-471c-8c33-fb52454d81c0', -- The system user responsible for prebuilds.
|
|
NOW(),
|
|
NOW()
|
|
FROM default_org;
|