summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-12-02 13:20:15 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-12-02 13:20:15 -0400
commitdf5666964d5479515428efb7471f4be6436ed263 (patch)
treee843873356fe1ecef32d04a86633a8a4d9ae2c58
parent3404992a14c761fe7171b4f03f0a1d4fd1f4bf94 (diff)
comment
-rw-r--r--doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment b/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment
new file mode 100644
index 000000000..dbfb7c0db
--- /dev/null
+++ b/doc/bugs/regression_with_S3_creds_not_used/comment_1_df5416ee63c8f026f3b3c77c74b67ce4._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-12-02T17:11:47Z"
+ content="""
+I tried reproducing this with the current version of git-annex on windows,
+and didn't see the problem. The creds file was used when the AWS_*
+environment variables were not set.
+
+What was the version of git-annex that was working before this reversion?
+
+Does the creds files corresponding to the uuid of your S3 remote exist?
+Does it contain 2 lines, for the access key and secret key, respectively?
+
+The webapp failure message seems to indicate that git-annex is has found
+creds, but they somehow have the wrong values. Does the s3ErrorAccessKeyId
+that you redacted match the access key that you told git-annex to use?
+(Note that it should be ok to show the s3 access key as long as you don't
+also show what the secret key is AFAIK.)
+"""]]