https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# s3gw
a
This message was deleted.
s
🤦 my bad, I somehow forgot to consider those breaking changes from the deployment point of view, especially the env var name. The command itself is unexpected, because now you should not need that at all (although it will likely output an error for 'unknown command'). I'll adjust the release notes after lunch.
👍 2
b
There is also https://github.com/aquarist-labs/s3gw/issues/819 which lead me to the fact that this was the necessary change to fix my compose file
s
ah, the compose file, yeah, we noticed that was broken late last week during out testing game day, but that wasn't deemed particularly relevant at the time because we assumed (silly, I know) that no one was actually using it. We'll prioritize fixing it for this cycle.
b
It’s pretty useful to set up a local s3 compatible service. I’m using it for local development and in the CI/CD pipeline
🙌 1
s
great to know, honestly. It's been hard finding feedback on use cases out there, and this more than emphasizes the imperative to ensure proper compatibility and maintenance of existing scripts and files (like docker-compose.yaml) as we move forward.
👍 1
@billions-secretary-56562 release notes will be updated for the container image options issue, but the env variable would require adjusting release notes as far back as v0.21.0 I believe. We'll just have to ensure the various scripts and the docker-compose.yaml file will be adjusted soon. In the mean time, this is what the release notes should look like, and you might want to take a look at the Advanced Usage documentation to know more about the options the entrypoint for the container now takes.
b
looks good and leads people to the right place. The advanced usage link leads to an ASCII fail whale for me
s
oh boy, I wonder if the doc build is broken again and somehow I have this cached - give me a sec
b
There are 3 hard things in computer science, off by one errors and caching ;-)
s
so true
sorry, I've tried 2 different browsers, clean caches, and my phone, and it opens just fine - no idea what may be happening
b
I’ll switch computers, let’s see
s
b
same whale on my old intel mac
The github link works though
s
this might be a CDN thing, I suppose - I'll check with others to see if they are bit by this as well
b
I assume so too. I’m accessing it from germany
So before you could pass the RGW-RELAXED-REGION-ENFORCEMENT parameter, it looks like this is no longer supported to be passed through?
s
you can still pass it, just provide a 
-- --rgw-relaxed-region-enforcement
etc
b
or do I use the --- separator`?
ok, just saw that 🙂
s
tbh, first time I'm seeing that option used in the wild, which is quite interesting 🙂
b
My employee had a problem to create the bucket without that option
s
we may need to check out why that happens, it's odd that's needed
b
he searched for quite a while and found that the error message could be suppressed by that switch
s
I'll keep that in mind and check it out
out of curiosity, how's that bucket being created? via the UI or some other way, APIs maybe?
b
using the amazon java sdk lib
for java
s
ack, thanks, will take a look and see if we can reproduce that somehow
b
Copy code
this.s3Client = S3Client.builder()
        .region(Region.AWS_GLOBAL) // Not needed by Ceph, but required by the AWS SDK
        .credentialsProvider(() -> AwsBasicCredentials.create(accessKey, secretAccessKey))
        .endpointOverride(URI.create(endpoint))
        .forcePathStyle(true)
        .build();
this.s3Client.createBucket(request -> request.bucket(bucketName))
This is the gist of it ;)
s
awesome, thanks for sharing, that will help 🙂
b
It is possible that he made a mistake, he’s a junior programmer and I am refactoring/cleaning up now.
s
There's also a fair chance that this is some assumption we made on our end as well, especially given we don't deal with regions per se. And assuming things about S3 dialect is a critical sin in this line of work.
b
I can imagine 😄 As we’re not using regions locally as well, it was a surprise that this was missing. I’m also not sure if there is a better S3 java api. This is the one we found
Copy code
RGW_DEFAULT_USER_ACCESS_KEY: "test_user"
RGW_DEFAULT_USER_SECRET_KEY: "test_secret"
Are these gone now? this worked pre 0.21
s
ah, I see - afaict, by specifying a region one kicks a bit of logic that basically says "oh, we don't have any of that, go away", where we should probably say "nope, you're good" - I'll create an issue for this to be worked soon
I don't think they have, although we plan on abstracting that at some point in the near future, but let me check if something changed real quick
b
I see, these seem to have remained the same according to the config-s3gw.md
s
still there, although the defaults have been 
test:test
b
I change that so I see that I’m using the correct credentials. test/test also has the disadvantage that you might mix them up and not notice
s
yeah, the 
test:test
thing should be changed as well at some point -- they've been around since our first driver implementation, and just lingered...
b
temporary solutions tend to stick 😄
s
yeah, we have a bunch of paper cuts that need to be tended to, hopefully Q1 next year
2 Views
Open in Slack
PreviousNext
Powered by