Philip Ardery

@fabpot @nicolas-grekas thoughts?

I don't have any pending db updates to test this. I was always suspicious that the cache clearing didn't work, but didn't have technical proof. If the issue you described...

I've also been using `terminus drush . -- cc all` to clear cache after running the deployment command. Is the database update command you are using `terminus drush . --...

thanks. Hopefully this issue will be fixed, thanks for opening it.

thanks for the info @chrisgross. Hopefully someone from Pantheon will chime in soon, since people realying on these arguments without knowing that they don't do anything could run into major...

I am not sure about the redundant `ACCEPT-UPSTREAM` and `UPDATEDB` arguments that @chrisgross mentioned. The [code](https://github.com/pantheon-systems/terminus/blob/adcff91294962f46ab7b807773bf53c4fc6b38ed/src/Commands/Upstream/Updates/ApplyCommand.php#L51-L52) I am looking at doesn't seem to suggest that said problem exists, but I...

thanks for the info @chrisgross!

I created patches.json and put the patch in there. I already had composer-patches installed and enabled from previous usage. I did bump the version to the latest 2.x beta from...

@cweagans Here is what I did: 1. remove `patches.json` 2. remove `web/modules/composer` 3. remove `patches.lock.json` 4. move my patch from `patches.json` (deleted) to `composer.json` in order to follow the [documentation](https://docs.cweagans.net/composer-patches/usage/recommended-workflows/#add-a-patch-to-your-project)...

My analysis seems to be correct. Once I removed the package then re-added it, the patch was triggered. However, I had to break this into two separate commits to make...