Thanks for considering my problem intriguing. I didn't find your comment dismissive at all and I appreciate your thorough response. Also your ideas are interes

Thanks for considering my problem intriguing. I didn't find your comment dismissive at all and I appreciate your thorough response. Also your ideas are interesting! The last one especially. > But if you have written the service such that you can reject a deployment unless you're sure it worked, you are technically free to use quite stupid ways to store the data because worst case the deployment just fails and the old code chugs on. I do and there's lots of error handling, so I'm not worried about doing a fun idea like editing a user profile via API. Your suggestions have my gears turning.