As title states, the drush.yml generation won't work if the project is using varnish, due to the search using the APPLICATION_NAME as parameter. If the project is using varnish, the upstream will actually be the varnish application and not the app itself.
We just noticed the issue as we tried releasing a project with varnish and the drush URL didn't change from the master branch to the upstream URL.
We don't have a suggested fix that could satisfy all the possible use cases yet.
update: varnish doesn't leave any traces in the PLATFORM_RELATIONSHIPS variable nor in any other environment variable, so not sure what the best approach would be to detect setups that have varnish.. we went with skipping the application name condition, but this wouldn't work with multi-app setups that may or may not involve varnish.
As title states, the drush.yml generation won't work if the project is using varnish, due to the search using the APPLICATION_NAME as parameter. If the project is using varnish, the upstream will actually be the varnish application and not the app itself. We just noticed the issue as we tried releasing a project with varnish and the drush URL didn't change from the master branch to the upstream URL. We don't have a suggested fix that could satisfy all the possible use cases yet. update: varnish doesn't leave any traces in the PLATFORM_RELATIONSHIPS variable nor in any other environment variable, so not sure what the best approach would be to detect setups that have varnish.. we went with skipping the application name condition, but this wouldn't work with multi-app setups that may or may not involve varnish.
Many thanks for all this great work!
Cheers, Alex.