Document that a table can be dropped in a single MR
What does this MR do and why?
This previous documentation insisted on separating in 2 MRs but we
couldn't think of any reason this was necessary apart from slightly
derisking if it turns out that the application still needed the code.
Practically there is no reason dropping the table can't happen in the
same MR in a post_migrate
.
This also doesn't conflict with our goal of not doing critical
migrations in post_migrate
as these only remove stuff so it wouldn't
actually be a problem if it was skipped.
This was also discussed in Slack at https://gitlab.slack.com/archives/C02JRAY273M/p1666984254650949
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.