0 Fork 0

Files

T

ToddandJeff Mitchell bbfef2802f Placeholder Plugin Providers for Repos and added testPlugin struct (#1532 )

* Create minimalistic plugin map and test plugin.

* Pass secrets and attributes to the plugin when creating catalogs or sets.  Add tests for CreateSet and CreateCatalog repo methods.

* make fmt and extract out getPrivateCatalog and getCatalog helper methods.

* Exporting TestPluginServer so it can be used in the handlers.

* Keep separate persisted data from host catalogs lookups which facilitate passing it onto the plugins.

* Add TODO to merge get Catalog and get Persisted data.

* Adding tests for unimplemented being returned by the plugin.

* Use GetFields() instead of AsMap() to confirm attributes should be populated. Make clone consistent between catalog and sets.

Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>

2021-09-21 09:18:49 -07:00

generate

Skip hidden directories when generating version numbers (#1008 )

2021-03-17 14:45:13 -07:00

postgres

Placeholder Plugin Providers for Repos and added testPlugin struct (#1532 )

2021-09-21 09:18:49 -07:00

README.md

Organize DB Schema Migration Code and DB Init Checks (#842 )

2021-01-19 10:40:41 -07:00

README.md

migrations package

This package handles the generation of the database schema in a format that can be compiled into the boundary binary.

Organization

./generate: contains the makefile, code, and templates needed to generate the schema info.
./postgres: contains the versioned schema folders. The contents of these folders, except for dev should not be modified.

Usage

To regenerate the schema information into the format the boundary binary uses run make migrations or make gen to recreate all generated code.

The content of the folders under ./postgres are compiled into the boundary binary and when the boundary database init or boundary database migrate commands are executed they are applied in order of their version.

The ./postgres/dev directory contains schema files that are under development and are not included in a release yet and so it is the only directory where additions and modifications are allowed. When a boundary binary is built when this directory is not empty a special flag is required to run the boundary database init command to indicate the user is aware that this is a development release and running this command can result in a completely broken schema and dataloss.

When a new release is made the contents of the dev directory are moved into a new versioned directory.