PostgreSQL types in context based multi-tenancy

[xanderio]

Is your feature request related to a problem? Please describe.

When creating a PostgreSQL custom enum type via CREATE TYPE foo AS ENUM ('bar', 'foobar') inside the custom_statements block while utilising context based multi-tenancy, the statement is placed into the tenant migration. This will fail to execute this statement as soon as a second tenant is created. Types in this context are global for the entire database.

Describe the solution you'd like

A configuration option that a statement should be place in the non-tenant migration set.

Describe alternatives you've considered

Currently, the only workaround is manual intervention.

Express the feature either with a change to resource syntax, or with a change to the resource interface

postgres do 
  custom_statements do
    statement :foo do
      global? true
      up "..."
      down "..."
    end
  end
end

[CyanideDragon]

I will begin to work on this