Currently there is no way to do migrations for Components and Layouts tables in the Postgres database, because these collections can change between migrations. These collections were intentionally removed from the migrations toolchain, but there should be a system setup so that these tables can be modified in migrations, either by running the migration tool multiple times on start of the application or some other way.
Steps to Reproduce
Steps to reproduce the behavior:
Create any migration for the table components or layouts. This migration will not be run on these tables until the module restarts.
Expected Behavior
Migrations should be complete on each restart of the module.
Additional Context
Due to the design of Clay, it's necessary to remove components and layouts from the migrations toolchain, however, we should attempt to make it possible to modify the attributes on these tables.
TTaitFoster
commented
5 years ago 
Description
Currently there is no way to do migrations for Components and Layouts tables in the Postgres database, because these collections can change between migrations. These collections were intentionally removed from the migrations toolchain, but there should be a system setup so that these tables can be modified in migrations, either by running the migration tool multiple times on start of the application or some other way.
Steps to Reproduce
Steps to reproduce the behavior:
componentsorlayouts. This migration will not be run on these tables until the module restarts.Expected Behavior
Migrations should be complete on each restart of the module.
Additional Context
Due to the design of Clay, it's necessary to remove
componentsandlayoutsfrom the migrations toolchain, however, we should attempt to make it possible to modify the attributes on these tables.