AUTO_MIGRATE removed but still in .env.example and documentation

[joshmedeski]

I see the AUTO_MIGRATE functionality was removed, see 85c3d14

In the environmental variables, this should be removed. It would even be helpful to include an error message if that variable is set to true to let users know it is no longer supported.

[joshmedeski]

I noticed the migrations documentation talks about Hasura handling the migrations. It would be good to mention what the AUTO_MIGRATE feature does on HBP and how to combine it with Hasura's migrations.

[elitan]

Yes. Thanks for spotting this.

For reference: HBP now handles its own migrations (#507) and will handle its own metadata soon (#546).

[amal-chandran]

@elitan what are the issues with hasura based cli migrations? #546 #507
can we persist "AUTO_MIGRATE" env so that we can override the default behavior we can set "AUTO_MIGRATE" as true by default right ?

[elitan]

AUTO_MIGRATE is not really related to the fact that HBP will handle its own migrations and metadata.

AUTO_MIGRATE was previously used to auto migrate from HBP v1 to HBP v2.

Generally, I don't think we'll allow to opt-out of HBP's own migrations and metadata.