-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage with testContainers-go #711
Comments
@sergseven recently added an internal endpoint for updating some configuration parameters, aimed specifically at setting the external URL after starting the container with test containers, you can see a Java example in his PR: #659 (comment) Let me know if that's enough information is enough for you. We should probably document that endpoint in the README at some point. |
So, that looks like it might be helpful, thanks! But, at the moment, it looks like it can only be used to change the ExternalUrl. https://github.com/fsouza/fake-gcs-server/blob/main/fakestorage/config.go I can submit a patch for changing the public host, if that's acceptable? |
@majelbstoat ohh sorry I misread your message. Yeah, that's acceptable, feel free to send the PR adding support for overriding the public host! |
Cool, PR here: #712 :) |
I'm trying to programmatically start fake-gcs-server using testcontainers-go. Example:
As with other folks, I can
curl --insecure http://localhost:XXXX/storage/v1/b/sample-bucket/o
and see my files in there, whereXXXX
is the mapped external port, but I can't retrieve them using the storage client.From other issues, I believe this is because I'm not setting a public host. My problem is, I don't know what the full public host will be until after the container starts, because that's when I get the mapped port.
As others have note,
-public-host 0.0.0.0
and-public-host localhost
don't work, so I have this circular dependency which I can't figure out how to break.The text was updated successfully, but these errors were encountered: