Hi guys,
we are giving a look to your great work here at GeoSolutions. We are evalutaing it to be adopted in some of our pipelines (in that case we hope to contribute back!).
Our initial test shows that, given the -deploytoproduction argument, the first import is directly moved to the public schema. The sunsequent imposm diff commands directly apply diffs to the public schema.
The latest is not very well documented on the imposm3 docs, and I quite do't understand how/why the diff command chooses the schema to apply diffs on.
My initial thought was that diffs were applied to import schema but, yes, in this case the import schema is empty because of the initial -deploytoproduction argument, so it couldn't apply diffs on that... My guess is that imposm diff only writes to public, by default?
A related question is: how do you deal with intermediate checks on imports or rollbacks in case of failures?
Hi guys,
we are giving a look to your great work here at GeoSolutions. We are evalutaing it to be adopted in some of our pipelines (in that case we hope to contribute back!).
Our initial test shows that, given the -deploytoproduction argument, the first import is directly moved to the public schema. The sunsequent imposm diff commands directly apply diffs to the public schema.
The latest is not very well documented on the imposm3 docs, and I quite do't understand how/why the diff command chooses the schema to apply diffs on.
My initial thought was that diffs were applied to import schema but, yes, in this case the import schema is empty because of the initial -deploytoproduction argument, so it couldn't apply diffs on that... My guess is that imposm diff only writes to public, by default?
A related question is: how do you deal with intermediate checks on imports or rollbacks in case of failures?