Maximum execution time of cloud/up

[jamesmacwhite]

I recently had to perform a database migration which involved modifying over 1,000 elements, to move data from an existing field to another. What I seem to have hit was the maximum execution time of cloud/up.

./craft cloud/up
---
Error running command [cloud/up]: The process has been signaled with signal "9".
Command exited with code 1

The signal 9 suggests the maximum execution time and forced the process to be ended.

I was operating under the rule of all commands would have a maximum of 15 minutes, but the timeframe for the cloud/up command seemed to be less than this. When running locally the time for the migration was under 15 minutes.

In order to complete this migration, I had to throw the production environment into maintenance mode, take a database backup, copy it down to local dev to run the migration locally then copy the database back up to the production RDS database, then re-run cloud/up to clear the failing cloud/up command because of the pending DB migration, which had now been run and added to the migrations table.

I could have used the queue, but the element type being modified was from a plugin and not a native element type, so the resave controllers weren't available in this case.

I'm just wanting to clarify if the cloud/up command does in fact have a shorter timeframe than 15 minutes?