the zip files that 0.1.0 had aren’t there in 0.2.0 or https://github.com/atomisthq/pod-atomisthq-tools.docker/releases/tag/v0.3.0

I can’t find an example of a non-archived (zip or tgz) artifact/url in any of the manifests. is it supported? if it’s not, let’s just revert my PR

I'll just revert

thanks. sorry for the mess 😞

no worries ;)

I reverted it now.

😌

(ns s3-utils
    (:require [com.grzm.awyeah.client.api :as aws]
              [com.grzm.awyeah.credentials :as credentials]))

(def s3 (aws/client {:api :s3
                     :region "eu-west-1"
                     :endpoint-override {:protocol :http
                                         :host "127.0.0.1"
                                         :port 9000}
                     :credentials-provider (credentials/basic-credentials-provider
                                            {:access-key-id     "minioadmin"
                                             :secret-access-key "minioadmin"})}))

and this is what I get in the REPL

s3-utils=> (aws/invoke s3 {:op :ListBuckets})
{:cognitect.anomalies/category :cognitect.anomalies/fault, :cognitect.anomalies/message "java.net.http.HttpConnectTimeoutException: HTTP connect timed out", :com.grzm.awyeah.http-client/throwable #error {
 :cause "HTTP connect timed out"
 :via
 [{:type java.util.concurrent.CompletionException
   :message "java.net.http.HttpConnectTimeoutException: HTTP connect timed out"
   :at [java.util.concurrent.CompletableFuture encodeRelay "CompletableFuture.java" 368]}
  {:type java.net.http.HttpConnectTimeoutException
   :message "HTTP connect timed out"
   :at [jdk.internal.net.http.MultiExchange toTimeoutException "MultiExchange.java" 581]}
  {:type java.net.ConnectException
   :message "HTTP connect timed out"
   :at [jdk.internal.net.http.MultiExchange toTimeoutException "MultiExchange.java" 582]}]

"HTTP connect timed out" sounds simple enough; but I don’t know how to approach this… I don’t know if it ends up connecting to some other endpoint, failing that

Can you try :hostname instead of :host

💡 lovely, that’s something I can work with

(aws/invoke s3 {:op :ListBuckets})
{:Error {:HostIdAttrs {}, :Message "The request signature we calculated does not match the signature you provided. Check your key and signing method.", :CodeAttrs {}, :ResourceAttrs {}, :RequestIdAttrs {}, :HostId "dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8", :MessageAttrs {}, :RequestId "17730AB06E4D9C86", :Code "SignatureDoesNotMatch", :Resource "/"}, :ErrorAttrs {}, :cognitect.anomalies/category :cognitect.anomalies/forbidden}

things to get sorted now: how to use it without credentials at all (its bucket can be made public); or how to fix the signature…

@U015879P2F8 thanks again. now if I’d only remember where I got that :host from. suddenly, all open tabs do say :hostname 🙈

No problem. Not sure on the other error, but some googling seems like it may be related to the port number not being included properly in the signature. If you can start minio on port 80 you could confirm whether or not that’s the source of the issue.

And probably leave the port out of your override settings if you do that test.

thanks I should be able to take it from here. I still feel embarrassed about being so lost in the first place — would there have been some way to have debug logging; or better yet, a debugger to use from the REPL…? :face_with_spiral_eyes:

Not sure if there’s additional logging from the library that would’ve shown you where it was trying to connect. My inclination probably would’ve been to launch wireshark or configure proxying through something like fiddler or mitmproxy and then you probably would’ve seen that it was trying to connect to real S3 endpoint urls via http on port 9000 and realized your override wasn’t configured completely.

thanks for sharing!

But since I couldn’t I poked around in the source for a couple minutes and saw what params it was destructuring

ah can you share that location with me? I’d love to have a look and have just started browsing them

I could have had a good look here! https://github.com/grzm/awyeah-api/blob/0ead32ccc3504f5e654ebb98f718d5719c8cd8fe/dev/user.clj#L14

https://github.com/grzm/awyeah-api/blob/main/src/com/grzm/awyeah/client.clj line 59 is the method that destructures the endpoint config

thanks again 🙂

ohh I found something https://github.com/grzm/awyeah-api/blob/0ead32ccc3504f5e654ebb98f718d5719c8cd8fe/src/com/grzm/awyeah/client/api.clj#L25-L58 💡

ℹ️ got the signatures to be accepted by changing minio to listen on 80, so the requestHost would end up as localhost instead of (before) localhost:9000. 🥳

@U015879P2F8 I’m afraid it took me to figure out how to look at minio’s audit logs first before I’ve tried going with this, what was your suggestion all along.

Glad to hear you got it sorted 🙂

https://github.com/babashka/http-client

• built into babashka, works in clojure if you want to eject • built on the rock-solid java.net.http

I don't know about ignoring ssl error, but at least with java.net.http it looks like it's possible https://stackoverflow.com/a/52995420/239678

Also see https://github.com/babashka/http-client/blob/main/API.md#-sslcontext

> :insecure - if true, an insecure trust manager accepting all server certificates will be configured.

Cool, thanks. I created the SSL context, but not sure to which key in opt to bind in the request of (post url opt) ? Tried {:ssl-context sslc} but post does not accept it as is appears

https://github.com/babashka/http-client/blob/main/API.md#babashka.http-client/client

Does post accept the same parameters as request ? This does not seem to work

(def client (http/client
             {::ssl-context (http/->SSLContext {:insecure true})}))
(def resp (http/post "" {:client client} ))

s/::ssl-context/:ssl-context/

Yep, caught that one as well )

you probably also want to merge in default-client-opts

i'm just sittin here reading the api docs, same as you 🙂

thank you for your effort) It's probably not related but post can't resolve localhost. (No name matching localhost found) curl has no issues. Is there another context i am missing

I don't know. The StackOverflow thread I linked has some options about hostname verification

Can't you give the https server a self-signed cert with the right hostname?

This is plan B, indeed. It appears the error No name matching localhost found does relate to ssl. Will need to explore

@U96LS78UV There is a fix on master for this, please try the --dev-build

Did you mean the other way around, fixed in dev? I have to say I don't know what to you mean by --dev-build @borkdude

master =d ev

bash <(curl ) --dev-build --dir /tmp

Yes, it been fixed indeed, thank you!

cool, I'll probably release a new bb tomorrow then

fixed in 1.3.182

The installer script still installs the v 1.3.181, have checked now, by the way. https://github.com/babashka/babashka/releases/download/v1.3.181/babashka-1.3.181-macos-aarch64.tar.gz

whoops, should be fixed now

(barring github caching)

Yes, it's updating, you are a Flash: ) ⚡