Finer control on file writing / coping with a GCS bucket without delete

[mkeskells]

We have a need to have a finer grain of control of the files written.
We want to configure GCS buckets without delete permission, so we want to be able to write files with a suffix or similar

Some background as to why we want this

• For us the downstream processes can cope with duplicate records, but cant cope with records going missing (e.g. you write a file, but commit fails, connect stops, and on restart the storage parameters have changed (or for any other reason we store less /different content in the file)
• If the file had been consumed (by a downstream process) and indexed then the index would not be valid
• Its also nicer to ensure that we cant accidentally delete data that we may legally have to keep for 7 years ...

Its a relatively simple process to detect and cope with I believe, but not a current capability that is configurable as I understand it.

For us any suffix on the filename would be OK, but there are probably other use cases that may want more specific control

What are you thoughts on this?