Fork me on GitHub
#aws
<
2018-12-20
>
alexmiller00:12:38

^^ for general info

alexmiller00:12:09

I think in this particular case, it’s fixed in newer versions of jetty and those may get bumped in the deps chain soon

aaelony01:12:18

cool, thanks once again

aaelony01:12:57

sheesh to illegal access... Clojure is not a crime! ;)

viesti14:12:30

0% cat deps.edn
{:deps {org.clojure/clojure {:mvn/version "1.10.0"}
        com.cognitect.aws/api {:mvn/version "0.8.158"}
        com.cognitect.aws/endpoints {:mvn/version "1.1.11.467"}
        com.cognitect.aws/s3 {:mvn/version "680.2.370.0"}
        com.cognitect.aws/apigateway {:mvn/version "668.2.364.0"}}}
[email protected] dev /tmp
0% clj -Srepro
Clojure 1.10.0
user=> (require '[cognitect.aws.client.api :as aws])
nil
user=> (def apigw-client (aws/client {:api :apigateway}))
2018-12-20 16:09:35.111:INFO::main: Logging initialized @12592ms
#'user/apigw-client
user=> (aws/invoke apigw-client {:op :GetRestApis})
{}
user=> ^D
[email protected] dev /tmp
0% aws apigateway get-rest-apis
{
    "items": [
        {
            "id": "6e071va237",
            "name": "chatAPI",
            "createdDate": 1479113133,....

viesti14:12:48

wonder where to look next

alexmiller14:12:49

is the problem that you don’t have any or that you can’t see them?

alexmiller14:12:03

a check with aws console would tell you the answer

alexmiller14:12:32

iam may also be affecting what you see I presume

alexmiller14:12:01

oh, you checked at the end, I didn’t see that

alexmiller14:12:46

I believe the request / response stuff is in the meta of the op return - that might tell you something

viesti16:12:01

haa, there’s stuff in the (-> (meta response) :http-response :body slurp)

viesti16:12:12

I guess it’s just not deserialized?

viesti16:12:50

user=> (-> (meta response) :http-response :body slurp)
"{\"_links\":{\"curies\":[{\"href\":\"",\"name\":\"authorizer\",\...

chrisulloa16:12:39

In other SDKs like the javascript SDK, the http response body is a string. Probably makes sense because I don’t think response body is consistently json across all endpoints.

viesti16:12:03

yeah, S3 api is XML

viesti16:12:10

over 10 years old

viesti16:12:39

Api Gateway is this funny Hypertext Application Language (HAL) thing https://docs.aws.amazon.com/apigateway/api-reference/index.html

viesti16:12:52

would be well suited for Datafy/nav I guess 🙂

chrisulloa16:12:54

I’ve never seen HAL before interesting

viesti16:12:18

some other aws api uses HAL too, don’t remember which now

viesti16:12:43

where’s my rebl now

viesti16:12:38

but hum, trying to grok how the deserialization is done in aws-api

viesti16:12:56

anyway, response in metadata is a neat thing, it means the lib is usable even though there isn’t a parser for the response yet

alexmiller17:12:32

if it’s not yet, it would be good to file an issue for aws-api

viesti17:12:59

filed https://github.com/cognitect-labs/aws-api/issues/30, just had to make sure I did’t do something foolish myself 🙂