Timothy Messier
0f19009cea
This adds new columns to the wh_user_dimension to provide additional
data from OIDC that does not apply to Password Auth.
Note: Given the specifics of the data, it is possible these columns may
be used by other auth methods in the future, hence the lack of `oidc` in
the column names.
The specific columns are:
- auth_method_external_id
For OIDC this is the Issuer
- auth_account_external_id
For OIDC this is the Subject
- auth_account_full_name
For OIDC this is the account's Full Name, and can be `None`.
- auth_account_email
For OIDC this is the account's Email, and can be `None`.
For all of these new columns, they will be `Not Applicable` if the auth
method is Password.
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 fordevshould 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.