Address Bucket Existential Bug
Opened this issue · 2 comments
Whenever creating a new bucket, sometimes you get a bucket does not exist when you try to sync with it. Right now I have a 5 second wait, but that's super hacky and doesn't always work. Look into confirming the bucket's existence after creation.
I was not able to resolve the existential detection issue directly. headBucket(), listObjects() both were ineffective in guaranteeing the bucket was ready for "web" configuration to be attached.
I ended up resorting to a 15 second wait on every bucket that gets created, and we use collect pull to wait on them all together. Which is a little gross, but it gets the job done.
This is sort of weird. But OTOH it only comes up when first creating a bucket, right? With proper advisory logging via the CLI, we could probably bump it to 30 seconds or a minute just to be safe. “Giving AWS a minute to get that bucket created…"