Add elasticsearch support to tugboat.

[KeyboardCowboy]

Resolves #387

[KeyboardCowboy]

I was trying to find a way to test my changes by generating a more robust config file and testing it against a more complete example. The test runner doesn't seem to be able to locate this file, though, so I'm not sure if I'm doing something wrong or if there's a better way to test my work.

[justafish]

@KeyboardCowboy the way we're currently testing it is by having the Tugboat file generated match the one we're using to create a Tugboat environment - bit of a hack, but unfortunately we can't generate a tugboat configuration on the fly. If you add elastic search to .tugboat/config.yml then that should be fine. Is there anything we can add to verify that elasticsearch has started correctly and is usable by Drupal?

[justafish]

@KeyboardCowboy the way we're currently testing it is by having the Tugboat file generated match the one we're using to create a Tugboat environment - bit of a hack, but unfortunately we can't generate a tugboat configuration on the fly. If you add elastic search to .tugboat/config.yml then that should be fine. Is there anything we can add to verify that elasticsearch has started correctly and is usable by Drupal?

[KeyboardCowboy]

I adjusted the .tugboat/config.yml file with the redis and elasticsearch entires to match what the build action should be adding, but the test is failing the file comparison on line 12, which appears the be the empty line between the mariadb dependency and the commands. Is there a way to view the file the action is generating to compare the two side-by-side? Otherwise what's the recommended way to test the output?

[deviantintegral]

@KeyboardCowboy that's a great question. From what I can tell, since diff also sets an error exit code if it fails we can use that, and get the advantage of not having to replicate this locally.

I pushed up a commit to this PR changing that, and you can see the test error in the CI logs. I'll let you fix it!

[KeyboardCowboy]

@KeyboardCowboy that's a great question. From what I can tell, since diff also sets an error exit code if it fails we can use that, and get the advantage of not having to replicate this locally.

I pushed up a commit to this PR changing that, and you can see the test error in the CI logs. I'll let you fix it!

Thanks, Andrew. It looks like it's working now. Do I need to do something about the sass/JS compilation error? I'm not sure that has anything to do with my changes.

[justafish]

If you have a look at the error log you can see it failed at downloading the DDEV images, so you can just re-run that test https://github.com/Lullabot/drainpipe/actions/runs/7964643194/job/21742704685?pr=413