I'm moving this task into the current sprint as it is actually a better descriptor of the work I had been tagging against T127133: - which I can close out if I bring this one in instead.
I'll re-submit those patches against this one
I'm moving this task into the current sprint as it is actually a better descriptor of the work I had been tagging against T127133: - which I can close out if I bring this one in instead.
I'll re-submit those patches against this one
Turning logging on normally involves manually enabling the setting in the UI under administer/admin/setting/misc - however we need to turn it on without it running the sql to create the triggers and then running that manually.
Ideally the steps would happen in the following order ....
First (ie. these have to be before later steps but not necessary 1,2,3
b) Create the log table database on live, give the mysql user permission to create tables & edit them in this DB
Once the setting metadata is deployed & flushed
Actual deploy
Dev installs
Note that if we need to do this in build kit we should probably deal with the issue of our buildkit being massively out of sync with the upstream one at the same time (possibly rebranching master & re-applying our patches selectively).
I feel like this is a follow on task. Noting this makes me inclined to enable the logging manually or via drush at time of deploy rather than put it in the upgrade script.