We don't need the SDG Target features in the NZ Justice version of
ImpactOSS so we want to delete them from it.
Changes
This commit deletes the SDG Target features from the application. This
includes the following tables and all of their corresponding
associations, controllers, factories, models, policies, routes,
serializers, and specs:
sdgtarget_categories
sdgtarget_indicators
sdgtarget_measures
sdgtarget_recommendations
sdgtargets
It does not delete the groups_sdgtargets_default field from the
Taxonomy model.
Considerations
The database migration that removes the tables is reversible, with the
following caveats:
It recreates the dropped tables using the statements in schema.rb,
which were taken from the version in nz-justice-development at the
time of this commit. Right now, there aren't any pending PRs that alter
those table definitions so they should be correct, but that could change
between the creation and merging of this PR.
Rolling back the migration will restore the tables, but it will not
restore any of their previous data. That data will only be recoverable
if we take and retain a database backup prior to deploying this change.
Context
https://github.com/impactoss/impactoss-server/issues/363
We don't need the SDG Target features in the NZ Justice version of ImpactOSS so we want to delete them from it.
Changes
This commit deletes the SDG Target features from the application. This includes the following tables and all of their corresponding associations, controllers, factories, models, policies, routes, serializers, and specs:
sdgtarget_categoriessdgtarget_indicatorssdgtarget_measuressdgtarget_recommendationssdgtargetsIt does not delete the
groups_sdgtargets_defaultfield from theTaxonomymodel.Considerations
The database migration that removes the tables is reversible, with the following caveats:
It recreates the dropped tables using the statements in
schema.rb, which were taken from the version innz-justice-developmentat the time of this commit. Right now, there aren't any pending PRs that alter those table definitions so they should be correct, but that could change between the creation and merging of this PR.Rolling back the migration will restore the tables, but it will not restore any of their previous data. That data will only be recoverable if we take and retain a database backup prior to deploying this change.