mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawmg0NqVniTETKYIWr6eyYRJnakNg0A6tRc 2015-02-04 21:42:22 +00:00 • committed by admin
parent 895b177647
commit 951a126470
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_2_ed27571352892fb5229b4daa50934308._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawmg0NqVniTETKYIWr6eyYRJnakNg0A6tRc"
nickname="Oliver"
subject="comment 2"
date="2015-02-04T21:42:22Z"
content="""
Hi joey,
It doesn't seem like embedcreds is set - `git show git-annex:remote.log | grep embed` doesn't yield anything.
The file you asked me to check does exist, and whenever I run `git annex enableremote` it gets updated with the contents of my environment variables.
I'm pretty certain the contents of these variables is correct - I'm using AWS' \"IAM\" options to allocate new access keys to my git-annex user, and would expect a different error if things were wrong there. I'll continue to double check my account settings.
"""]]