Multiline cron commands failing deployments in k8s about build-deploy-tool

[rocketeerbkw]

Discussed in tech directions. Depending on the schedule the user picks, the cron job could be scheduled in-pod, using go-crond and a crontab which does not allow multiline commands. The current multiline "feature" is only because yaml allows setting the value with a special syntax. If the user picks the wrong block scalar e.g., | instead of > they'll get an error.

We discussed just forcefully wrapping the command to a single line, but if the user added a \ as in the example above, that would just break the cron job. So the deployment would succeed, but the cron jobs wouldn't be working. We think that is a worse experience than having the deployment fail.

The only way to support multiline commands is to adjust the .lagoon.yml parser so that it accepts a sequence:

command:
  - drush cron

That may or may not be something we want to do. For now, we will update the documentation to warn about using multiline commands, and update the .lagoon.yml linter to throw an error on misconfigured commands.