TJ
TJ
Ahh I like it! I hadn't thought of it, but I totally agree, much better than trying to find it in the docs
fixed in c0e6f655e81fd2f0b042dae2f1f0fd1a59163be6 but I have to add a warning for people who manually assigned VPC to move it to up.json before I can do another release there
nvm, reverted that commit, I don't think there's any clean way to tell if it was manually configured or simply removed from up.json. I can't really introduce c0e6f65 without breaking...
Oops I missed this one! Up isn't really designed for individual Lambda functions unfortunately, it's tailored to HTTP applications only at the moment.
Niceeeee, time to undo some code :D
realizing this might not be a great option since it'd require people point their DNS to AWS before the zone is even created haha, which can't happen. It would have...
I just don't want two code paths, makes QA and docs a bit more tricky since this would only work for `up`-purchased domains. Maybe though, it would be a nicer...
Yep they'd be account-wide for use between applications. I have mixed feelings about it but yep haha
Actually, having second thoughts about this now because it would require two calls to SSM, or many more if the prefix is less specific. If "baking" in the variables (#547)...
It should work actually, but it's a bug hahaha... `up.json` should technically take precedence over the `AWS_PROFILE` env var, but I believe it's the opposite right now. I think `--profile`...