| I would prefer this to be handled entirely via documentation, where we document how to truncate this table, maybe even provide a script that assists them with it. Adding a setting adds additional complexity to PuppetDB (the setting itself, validation, code to use it, unit tests, integration tests) that may not be extra maintenance in the future. I don't know of any other migrations where we have done this. This isn't without precedent - there are already scripted truncation of tables via cron running at customer sites. |
