Todd KnightandMichael Gaffney
db9e1106a9
* feat(host): Add host plugin related schemas and tests This adds the schema files for host plugins, plugin based catalogs and plugin based sets. This also adds the protos and tests which utilize gorm to ensure the schemas enforce the constraints we expect. Along with this change was a migration which moved catalog names to the base type table so we can ensure all catalogs in a single scope, regardless of subtype, have a unique name. * Updated plugin schemas to do the following: - Add plugin_executable table - plugin table now also has scope_id and name w/ uniqueness constraints - host_plugin no longer has id_prefix column - host_plugin separates name and plugin_name - plugin_version table renamed version to symantic_version column. * Fix typo in delete_plugin_subtype trigger. Add update test for host plugins. * Update id prefixes. Fix public_id typos in protos and plugin_executable name in sql diagrams. * Created internal/plugin and moved base plugin structs to it and moved host plugin subdirectory to it. * Created internal/plugin and moved base plugin structs to it and moved host plugin subdirectory to it. * Add first pass at enums for OS and Arch supported by plugin executables. * Capitalizing the const enums for OS and Architectures. * Add comments to sql files. * Reviewer comments. Remove unsupported OSes and Archs from SQL and go constants. Add missing tests. * Be more permissive in the values the db accepts. The go logic can restrict which values it will allow getting populated into the db. * Removing constraints on which values can be placed inside operating_system and architecture columns. * Updating test helper functions to only create a single catalog or set. * Move files to new migration version. * Fixing job/plugin test. * Update table names, named a number of constraints, remove plugin version and executable tables. * Add constraints for plugin name and id prefix. * Rename constraint, remove unhelpful comment block. * Adding semantic version to plugin_host and set attributes to not null. * Remove semantic versioning from all locations. * Remove semantic_version from plugin_host table comment. * Fix op copy/paste error. Don't use deprecated errors methods. Update constraint names. Add docs. * Apply suggestions from code review Fixing constraint names. Co-authored-by: Michael Gaffney <mgaffney@users.noreply.github.com>
79 lines
2.5 KiB
PL/PgSQL
79 lines
2.5 KiB
PL/PgSQL
begin;
|
|
|
|
-- We are updating the plugin table here to have a scope id, since
|
|
-- subtypes of plugin should be scoped. We use 'global' as the default
|
|
-- just for the purpose of the migration since the scope cannot be null
|
|
-- and the one plugin that already exists (pi_system) can be globally
|
|
-- scoped. The immediately following statement removes this default.
|
|
-- We add a name so we can enforce that all plugins have a unique name
|
|
-- in a specific scope across all plugin subtypes.
|
|
alter table plugin
|
|
add column name wt_name,
|
|
add column scope_id wt_scope_id
|
|
not null
|
|
default 'global'
|
|
constraint iam_scope_global_fkey
|
|
references iam_scope_global(scope_id)
|
|
on delete cascade
|
|
on update cascade;
|
|
|
|
alter table plugin
|
|
alter column scope_id drop default;
|
|
|
|
-- Add constraints that enforce names are unique across all plugin subtypes
|
|
-- in a specific scope.
|
|
alter table plugin
|
|
add constraint plugin_scope_id_public_id_uq
|
|
unique (scope_id, public_id),
|
|
add constraint plugin_scope_id_name_uq
|
|
unique (scope_id, name);
|
|
|
|
|
|
-- insert, update, and delete plugin_subtypes are created since we are adding
|
|
-- subtyped plugins and we need to keep the base table plugin in sync with all
|
|
-- subtype tables.
|
|
create function insert_plugin_subtype()
|
|
returns trigger
|
|
as $$
|
|
begin
|
|
insert into plugin
|
|
(public_id, scope_id, name)
|
|
values
|
|
(new.public_id, new.scope_id, new.name);
|
|
return new;
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function insert_plugin_subtype() is
|
|
'insert_plugin_subtype() inserts sub type name into the base type plugin table';
|
|
|
|
create function update_plugin_subtype()
|
|
returns trigger
|
|
as $$
|
|
begin
|
|
update plugin set name = new.name where public_id = new.public_id and new.name != name;
|
|
return new;
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function update_plugin_subtype() is
|
|
'update_plugin_subtype() will update base plugin type name column with new values from sub type';
|
|
|
|
-- delete_plugin_subtype() is an after delete trigger function
|
|
-- for subtypes of plugin
|
|
create function delete_plugin_subtype()
|
|
returns trigger
|
|
as $$
|
|
begin
|
|
delete from plugin
|
|
where public_id = old.public_id;
|
|
return null; -- result is ignored since this is an after trigger
|
|
end;
|
|
$$ language plpgsql;
|
|
comment on function delete_plugin_subtype is
|
|
'delete_plugin_subtype() is an after trigger function for subytypes of plugin';
|
|
|
|
insert into oplog_ticket (name, version)
|
|
values
|
|
('plugin', 1);
|
|
|
|
commit;
|