TJ
TJ
Doing `if err.Object != nil {` is definitely unintuitive, I was trying `*js.Error` != nil as well. I think part of it is a documentation issue, I didn't even see...
I'm noticing it's really easy to accidentally bloat your client code. I have a few shared package with build tags, but then I'm pulling in all the server dependencies as...
The AWS site mentions that a “China legal entity is required for an account”, so there’s no way for me to test it unfortunately :(. Someone else already tried adding...
Darn, thanks for giving me access to test, looks like it's missing some features preventing parity for now. Looks like Route53 and ACM are missing as well, but those could...
thanks! definitely need some validation there
Hello! To update the warming functions you may need to delete and run `up stack plan/apply` again, those are part of the "stack". It should be fine to leave them...
from [this post](https://github.com/weaveworks/eksctl/issues/47) it sounds like a CGO issue—could you try changing the build hook to: ```json { "hooks": { "build": "CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o server *.go" }...
Hmm I'm not sure, I still haven't tried the API Gateway built-in auth stuff, I just use JWT at the moment for my stuff. Currently the CORS stuff is configured...
I've still never tried the AWS auth stuff—I'm not sure it really adds value—mine doesn't really follow the JWT spec but there should be some decent Go JWT packages out...
oh weird! I think I'm just printing them as they're received from AWS, should be ascending but I'll see if I can reproduce