Marcus, I can't speak for Swift, but the main reason there is no update current for S3 was time. I agree that the keys and timeouts should be adjustable, but the implementation of S3 ran much longer than my employer expected, and a compromise I had to make was matching the functionality of S3. Also, I am expected that S3 will be re-written in the next release to fit into the new storage architecture, and the limitation will be removed then.
Thanks, -John On Jan 24, 2013, at 3:02 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > What's the issue on this with never being able to reconfigure it > again? If I change my key or something in the database, does that > work, or is there some technical reason other than no UI set up? I > don't understand how it works well enough to get why you can't add it > after the zone creation, or change your credentials/S3 provider > afterward.
