-
Notifications
You must be signed in to change notification settings - Fork 29
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
S3 endpoint parameter missing?? #18
Comments
Is this where the endpoint is being replaced when passed https://github.com/jjneely/whisper-backup/blob/master/whisperbackup/whisperbackup.py#L83 ? |
I'm just passing a AWS Region to boto and letting boto "know" the endpoints for that region and connect. The above is how you would specify a different region. Its passed through here: https://github.com/jjneely/whisper-backup/blob/master/whisperbackup/s3.py#L31 If you are trying to use an S3 compatible service, probably some patches will be needed to be able to specify those endpoints. |
Right, but I think it would be more flexible if tool support passing optional endpoint parameters. we are trying to use it for IBM COS storage(similar to S3) and it would be very beneficial to pass endpoints for our scenarios instead of adding our regions->endpoint mappint in boto endpoint.json file. I can may be work on submitting a patch if you like. Don't think it would be hard. Please advise? |
I have tested in my local machine by adding --endpoint option to support our needs and it works. Tail of my dev log shows And bucket has wsp files Will be happy to create a PR once the author gives a go-signal. Please advise, thanks!! |
Test your restores! But yes, PRs welcome. |
yes restore works too with endpoint. Tried creating PR but it said permission denied. Is there some restriction to push commits to repo? |
Created PR #20 Logs for backup 2018-08-06-11:37:14;INFO;Scanning filesystem... Some logs after future backups Only change is passing endpoint argument to s3 script and if endpoint is specified connect using boto S3Connection. if not use the connect_to_region for bucket list and creation |
This is more of a question than issue. Am trying to use this tool for our graphite data backups to S3 and wondering where the endpoint is picked up or specified. We have our service endpoints where we store the buckets, but I don't see where it's being passed to tool or defaulted anywhere in script. Kindly advise
The text was updated successfully, but these errors were encountered: