This message was deleted.

apparently this only repros on certain stacks...

Hello! This is a known issue which I am literally rolling out the fix for as we speak. (But will take a day or two more to complete the database migrations, etc.)

ah, okay

The problem on our end is that we currently do not support case-sensitive Stack configuration. So it appears (just from the error message I am seeing) that you have two configuration values that only differ by case. e.g.

databasePassword

and

DatabasePassword

. If you remove one of those, you should be able to perform the update.

yeah, that's exactly what we have

Having case sensitive configuration should work ~soon. But for several issues, it’s been kind of a pain to fix. (And have had the limitation in our system for a while, unfortunately.)

Thanks for the info, I've managed to rename the offending config key and it's working again. Probably best practice to avoid duplicate names with only case differences

Probably best practice to avoid duplicate names with only case differences

Yes, I would recommend that if only to avoid programmer confusion. (For similar reasons that having variables

index

and

Index

in the same scope might not be ideal.) As always, please let me know if you have any other issues, feedback, or suggestions.