deploy overwrites existing s3 routing rules with 'generateRoutingRules' set to false

[cezarcarvalhaes]

We had an issue where when using gatsby-plugin-s3, it created an infinite re-direct loop on one of client-only routes. So we set generateRoutingRules to false. We then route our own routing rules manually and added to s3 for other client-only routes, only to find out that they get erased on every deploy from here on out. This might be due to the inner workings how aws-cli syncs.

It would be a nice feature to be able to write our own custom routing rules, and reference the json file inside the gatsby-plugin-s3 config options.

[andrew-knott]

Is there any resolution on this? How can we prevent manually added redirection rules from being deleted?