Fix Version/s: None
Once pg_sphere is installed and we agreed on obscore configurations (
DM-36701) we need to run migrations to add everyhting to each of the repos.
My initial idea is that migration script would just add obscore config to butler_attributes and create the obscore teable with a correct schema (which is based on config). For actual filling of the table from pre-existing data I want to implement a separate script which will run later, that way the migration can be short and we don't need a downtime for it. The population script can run concurrently with other users, so we should not need any disruption.
Just like for dimensions manager we'll have two separate migrations branches, one for the manager class itself, and another for configuration. It is also likely that we'll need separate migration branch for each repo, as each of them will heave an independent configuration. IT makes sense to start with a single repo as a demonstrator to show people how it's going to look like. It is also less critical for obscore to do everything right on the first iteration, we can always delete and re-create obscore table again.
Tim Jenness, one general comment - dax_obscore now has three commands that it adds to butler CLI - obscore-export, obscore-set-exposure-regions, obscore-update-table. I probably makes sense to transform all of them into one sub-command with three sub-sub-commands (e.g. butler obscore export). Let me know if you want me to do it on this ticket.
OK, I'll change that. I don't think we need a deprecation period, there should not be many users of those commands out there.
I added one more commit which makes "obscore" a separate command group.
Tim Jenness, this should be ready for review, we are still waiting for pgsphere so there is no rush. There are three packages involved:
Jenkins is running but it only covers daf_butler, I've done testing for the rest on my local copy of OGA repo.