TJ
TJ
looks correct in mine, possibly a race condition though I'll dig some more
sweet yea I saw that, I'll have to try that soon and verify, would be nice to clean that up! :D
interesting, haven't hit that one before, I'll try adding a DependsOn so those two deployments don't happen in parallel, hopefully that'll do the trick. Thanks for the report!
@tamagokun if you run `up stack` there should be some more detailed errors, may be a conflict with an existing domain name or something like that
@tamagokun No worries! Let me know if you hit something that doesn't seem obvious, sometimes the AWS error messages a bit obscure
Seems like a bug on their part to me kind of. If they let you define deployments in cloudformation they shouldn't race with each other, I'll try bringing it up...
I remember looking into it but I forget what the result was now, I think it was more expensive, but it would be nice to have it as an option...
hmm interesting, I'll dig through the docs and see if I can find which fields should be omitted where, might be a little tricky to test them all—thankfully I'm moving...
I'll try and check it out soon, I don't think too many people are hitting it but it should be pretty quick to add! I should have written down the...
Hmm unless I'm doing it wrong, it looks like Yarn doesn't symlink those modules in, it just uses Node's delegation of parent node_modules to resolve them