-
Notifications
You must be signed in to change notification settings - Fork 90
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
Ability to push to custom endpoint URL #1629
Comments
I assume you are talking about an object gateway endpoint, so that the client would talk to min.io instead of S3 (i.e. not what's in |
As I understand there are at least two mandatory entities in a quilt installation :
I am looking for a way to tell quilt to use specific s3-compatible storage, similar to the command below |
Makes sense. We are doing some planning work now on adding GCP support. Would you like to contribute in the open source? If so we can start with a design that solves both problems. |
I think what needs to happen here is that all of the naked S3 calls get wrapped with an abstraction and then, depending on the physical type of the wrapped storage layer, we dispatch the appropriate call. In theory S3, min.io, and GCP all support the same S3 v4 API. In practice... I'm not sure yet. |
@akarve we are looking for the same feature, use quilt to upload data to self hosted s3 endpoint. we defined the endpoint in config and credentials files, but it does not work hurdat.push('aleksey/hurdat', 's3://<self_hosted_s3_bucket>')
i confirmed we able to write to the on premise |
I tried this out but ran into the same problem as @cometta. I set up a local MinIO for testing using docker-compose: version: "3.8"
volumes:
bucket-data: {}
secrets:
access_key:
file: ./secrets/access_key.txt
secret_key:
file: ./secrets/secret_key.txt
services:
minio:
image: minio/minio:RELEASE.2020-12-03T05-49-24Z
volumes:
- bucket-data:/data
secrets:
- access_key
- secret_key
environment:
- "MINIO_ACCESS_KEY_FILE=/run/secrets/access_key"
- "MINIO_SECRET_KEY_FILE=/run/secrets/secret_key"
ports:
- "127.0.0.1:9000:9000"
command: "server /data"
Then configured credentials and profile using the AWS CLI with the above mentioned endpoint plugin. So now my profile looks like this: [default]
s3api =
endpoint_url = http://127.0.0.1:9000
s3 =
endpoint_url = http://127.0.0.1:9000
signature_version = s3v4
[plugins]
endpoint = awscli_plugin_endpoint and I have corresponding credentials [default]
aws_access_key_id = ****
aws_secret_access_key = **** I can configure a default registry using import quilt3
quilt3.config()
pkg = quilt3.Package()
top_hash = pkg.push("test/pkg", "s3://test-bucket", message="Hello World")
Do I need to supply the credentials differently? Should I make MinIO available under a domain instead of localhost for it to work? Thank you for any insights. |
Marking as duplicate of #1941 which already has a PR |
Hi.
I am using https://github.com/wbingli/awscli-plugin-endpoint to setup endpoint_url in aws config file for minio storage.
Is there a way to setup quilt to work with custom endpoint url?
The text was updated successfully, but these errors were encountered: