* Adding explicit MPL license for sub-package. This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Adding explicit MPL license for sub-package This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at www.hashicorp.com/licensing-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUS-1.1 * Rerun make gen This will pick up the last of the license changes * Revert "Rerun make gen" This reverts commit dbe0968bffd92745d8663c6940debae098395a6b. * Remove copywrite from generation script The current version of copywrite is not sophisticated enough to only apply the copywrite changes to certain subdirectories, so to avoid accidentally relicensing our api and sdk modules, we will stop running the copywrite script until such time that it can do the right thing. * License protobuf API as MPL The protobuf API files are used to generate the SDK, since we want the SDK to be MPL, the protobuf files must also be MPL. This extends to all protobuf files whose sources end up in the SDK directory, including: - internal/proto/controller/api - internal/proto/controller/custom_options - internal/proto/plugin It also includes the generated service directory in internal/gen/controller/api/services, since they are generated from the protobuf sources used for the SDK. * Change website license file name This makes the naming scheme consistent with the rest of the repository. * Add note on licensing to README * Set copywrite license to BUSL * Revert "Add note on licensing to README" This reverts commit 4d865a91a7a4f11605f0dc4609355d7e3c3cfffe. --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com> Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
84 lines
3.1 KiB
PL/PgSQL
84 lines
3.1 KiB
PL/PgSQL
-- Copyright (c) HashiCorp, Inc.
|
|
-- SPDX-License-Identifier: BUSL-1.1
|
|
|
|
begin;
|
|
|
|
-- By adding the name column to the base auth method type, the database can
|
|
-- ensure that auth method names are unique across all sub types.
|
|
alter table auth_method
|
|
add column name wt_name;
|
|
|
|
alter table auth_method
|
|
add constraint auth_method_scope_id_name_uq
|
|
unique (scope_id, name);
|
|
|
|
|
|
-- the intent of this statement is to update the base type's name with the
|
|
-- existing password auth method names.
|
|
update auth_method
|
|
set name = pw.name
|
|
from
|
|
auth_password_method pw
|
|
where
|
|
auth_method.public_id = pw.public_id and
|
|
pw.name is not null;
|
|
|
|
-- insert_auth_method_subtype() is a replacement of the function definition in
|
|
-- migration 07_auth.up.sql This new definition also inserts the sub type's name
|
|
-- into the base type. The name column must be on the base type, so the database
|
|
-- can ensure that auth method names are unique across all sub types.
|
|
create or replace function insert_auth_method_subtype() returns trigger
|
|
as $$
|
|
begin
|
|
insert into auth_method
|
|
(public_id, scope_id, name)
|
|
values
|
|
(new.public_id, new.scope_id, new.name);
|
|
return new;
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function insert_auth_method_subtype() is
|
|
'insert_auth_method_subtype() inserts sub type name into the base type auth method table';
|
|
|
|
-- update_auth_method_subtype() is a new function intended to be used in "before
|
|
-- update" triggers for all auth method sub types. It's purpose is to ensure
|
|
-- that the name column is syncronized between the sub and base auth method
|
|
-- types. The name column must be on the base type, so the database can ensure
|
|
-- that auth method names are unique across all sub types.
|
|
create or replace function update_auth_method_subtype() returns trigger
|
|
as $$
|
|
begin
|
|
update auth_method set name = new.name where public_id = new.public_id and new.name != name;
|
|
return new;
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function update_auth_method_subtype() is
|
|
'update_auth_method_subtype() will update base auth method type name column with new values from sub type';
|
|
|
|
create trigger update_auth_method_subtype before update on auth_oidc_method
|
|
for each row execute procedure update_auth_method_subtype();
|
|
|
|
create trigger update_auth_method_subtype before update on auth_password_method
|
|
for each row execute procedure update_auth_method_subtype();
|
|
|
|
-- delete_auth_method_subtype() is an after trigger function for subytypes of
|
|
-- auth_method
|
|
create or replace function delete_auth_method_subtype() returns trigger
|
|
as $$
|
|
begin
|
|
delete from auth_method
|
|
where public_id = old.public_id;
|
|
return null; -- results are ignore since this is an after trigger.
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function delete_auth_method_subtype is
|
|
'delete_auth_method_subtype() is an after trigger function for subytypes of auth_method';
|
|
|
|
create trigger delete_auth_method_subtype after delete on auth_oidc_method
|
|
for each row execute procedure delete_auth_method_subtype();
|
|
|
|
create trigger delete_auth_method_subtype after delete on auth_password_method
|
|
for each row execute procedure delete_auth_method_subtype();
|
|
|
|
commit;
|