I'm a +1 to doing this. The change to production is not too huge, so I think it's low risk. As I've said elsewhere, I've used this technique to do backups and analytics before to avoid putting load on production and it worked well. I personally think going without backups is a higher risk than the changes to production. Maybe it's a lower chance of failure, but I say higher risk because the consequence of not having backups when you need them is greater than the consequence of needing to roll back the config changes if something goes wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
