It's important that lazy-build try hard never to make things worse. Some things I think are essential before I'd be comfortable using it in a large project:
It needs to handle errors from S3 gracefully by falling back to the regular command (authentication errors, network errors, etc.)
It needs to time out if downloading or uploading from S3 is taking too long and fall back to the regular command
Ideally it also needs a way to be temporarily disabled without a code push (sort of covered by #9). That could either be some metadata in S3, or maybe a file elsewhere on disk (the "srv-configs" model?).
It's important that lazy-build try hard never to make things worse. Some things I think are essential before I'd be comfortable using it in a large project:
Ideally it also needs a way to be temporarily disabled without a code push (sort of covered by #9). That could either be some metadata in S3, or maybe a file elsewhere on disk (the "srv-configs" model?).
Anything else?