Currently, /edgedb-bootstrap.d is executed before migrations are
applied, which could be inconvenient if custom bootstrap relies on the
schema. This lets putting bootstrap parts in /edgedb-bootstrap-late.d
to be executed after the migrations have been applied.
Currently,
/edgedb-bootstrap.dis executed before migrations are applied, which could be inconvenient if custom bootstrap relies on the schema. This lets putting bootstrap parts in/edgedb-bootstrap-late.dto be executed after the migrations have been applied.