We’re using a quicksilver hook in our pantheon.yml file to sanitize our database from PII on tables that have 1.6M records (and growing) when the database is cloned from production. We’re running into a timeout error and I was wondering if we could perhaps have a timeout parameter for hooks for longer-running tasks?
So, I believe the issue here is that the current Quicksilver web scripts pass through nginx, and it is the web server that is imposing the time limit. There is therefore no good way to make this timeout configurable.
There was a vision for providing a different sort of Quicksilver script that would execute directly, without the need to pass through the web server. I don’t think that this feature is currently prioritized for any sprint at the moment, though.