Timothy Messier
8caaf3e076
This refactors the schema package and subpackages to support editions.
An Edition is a collection of sql migrations. A given boundary binary
can have multiple migration editions. The `schema.Manager` is updated to
apply the necessary migrations in the correct order, leveraging an
Edition's priority to determine the order in which the separate Editions
are applied.
The sql migration files are now nested under a directory for the
edition.
This also switches from the generated code to using embed, which
eliminates the need for the `make migrations` target and the generated
code. As such this commit removes the target and generated code.
See:
https://pkg.go.dev/embed
70 lines
2.0 KiB
PL/PgSQL
70 lines
2.0 KiB
PL/PgSQL
begin;
|
|
|
|
-- add the primary_auth_method_id which determines which auth_method is
|
|
-- designated as for "account info" in the user's scope. It also determines
|
|
-- which auth method is allowed to auto viviify users.
|
|
alter table iam_scope
|
|
add column primary_auth_method_id wt_public_id -- allowed to be null and is mutable of course.
|
|
constraint auth_method_fkey
|
|
references auth_method(public_id)
|
|
on update cascade
|
|
on delete set null;
|
|
|
|
-- establish a compond fk, but there's no cascading of deletes or updates, since
|
|
-- we only want to cascade changes to the primary_auth_method_id portion of
|
|
-- the compond fk and that is handled in a separate fk declaration.
|
|
alter table iam_scope
|
|
add constraint auth_method
|
|
foreign key (public_id, primary_auth_method_id)
|
|
references auth_method(scope_id, public_id);
|
|
|
|
-- iam_user_acct_info provides account info for users by determining which
|
|
-- auth_method is designated as for "account info" in the user's scope via the
|
|
-- scope's primary_auth_method_id. Every sub-type of auth_account must be
|
|
-- added to this view's union.
|
|
create view iam_acct_info as
|
|
select
|
|
aa.iam_user_id,
|
|
oa.subject as login_name,
|
|
oa.full_name as full_name,
|
|
oa.email as email
|
|
from
|
|
iam_scope s,
|
|
auth_account aa,
|
|
auth_oidc_account oa
|
|
where
|
|
aa.public_id = oa.public_id and
|
|
aa.auth_method_id = s.primary_auth_method_id
|
|
union
|
|
select
|
|
aa.iam_user_id,
|
|
pa.login_name,
|
|
'' as full_name,
|
|
'' as email
|
|
from
|
|
iam_scope s,
|
|
auth_account aa,
|
|
auth_password_account pa
|
|
where
|
|
aa.public_id = pa.public_id and
|
|
aa.auth_method_id = s.primary_auth_method_id;
|
|
|
|
-- iam_user_acct_info provides a simple way to retrieve entries that include
|
|
-- both the iam_user fields with an outer join to the user's account info.
|
|
create view iam_user_acct_info as
|
|
select
|
|
u.public_id,
|
|
u.scope_id,
|
|
u.name,
|
|
u.description,
|
|
u.create_time,
|
|
u.update_time,
|
|
u.version,
|
|
i.login_name,
|
|
i.full_name,
|
|
i.email
|
|
from
|
|
iam_user u
|
|
left outer join iam_acct_info i on u.public_id = i.iam_user_id;
|
|
|
|
commit; |