To run integration tests, just use: sudo make check
This will give you a report of all passes and failures.
To add an integration test, just add it to the TESTS variable in s3fs/test/Makefile.am
Make sure your test sources integration-test-common.sh and require-root.sh
Having many of these for every feature will help us avoid regressions and develop with confidence.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@230 df820570-a93a-0410-bd06-b72b767a4274
Add support for mulitple access id/secret access keys in passwd-s3fs file
This change applies to any passwd-s3fs files.
The format of the file is more robust, error checked and extended:
- as before, any line beginning with # is ignored
- any empty line is ignored
- any non-ignored line which contains a space or tab is an error
- any non-ignored line which does not contain a : separator is an error
The format of the file is:
[bucket:]AccessKeyId:SecretAccessKey
The bucket can now be specified to allow for multiple credentials.
A default entry is as before:
AccessKeyId:SecretAccessKey
Only one default entry is allowed, if more than one default entry
is found, that is an error. A default entry is not required, if the
bucket that is being mounted has its own entry.
If the user's .passwd-s3fs file is present but credentials cannot
be determined from it, then the system-wide /etc/passwd-s3fs will
be consulted (if readable by the current user).
This change is completely backward compatable with the existing
scheme and has been well tested.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@229 df820570-a93a-0410-bd06-b72b767a4274
Issue #102 --help command line
Issue #107 command line checking and other error checking
Issue #112 uses getopt_long now, but FUSE's own parser is still there
some command line checking is split between main() and the
helper function
Issue #117 command line option for credentials file
Issue #118 use of environment variables for credentials
Issue #119 support for a local passwd-s3fs file
Big checkin, many new lines of code.
Comand line option checking is now more robust and does quite
a bit of error checking before handing the mount off to FUSE.
Cleaned up the code and made several new functions from
existing code
Many ways to supply credentials now and there is a precedance
order followed.
--help is helpful
git-svn-id: http://s3fs.googlecode.com/svn/trunk@227 df820570-a93a-0410-bd06-b72b767a4274
If the "public_bucket=1" option is used, then
the command line options for Access Key ID and
Secret Access Key are ignored as well as the
/etc/passwd-s3fs file
Internally, the "Authorization: AWS ..." header
line is not included in the header.
Tested on a public bucket and it appears to work.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@221 df820570-a93a-0410-bd06-b72b767a4274
=========================
Removed extra space in the message emitted by --version
M s3fs/src/Makefile.am
==========================
Added the .h files to the s3fs_SOURCES. These files
were not being included in the .tar.gz file when
"make dist" was being executed. This was sourced
as an error with the "make distcheck" target.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@217 df820570-a93a-0410-bd06-b72b767a4274
Used the compile time VERSION define
Version message conforms to GNU Coding Standards
git-svn-id: http://s3fs.googlecode.com/svn/trunk@213 df820570-a93a-0410-bd06-b72b767a4274
readme.txt has been moved to README
removal of Eclipse CDT project files
git-svn-id: http://s3fs.googlecode.com/svn/trunk@212 df820570-a93a-0410-bd06-b72b767a4274
This is probably wasted work though since issue #99
is going to get the build process on autotools.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@207 df820570-a93a-0410-bd06-b72b767a4274
Tricky way to generate the distribution tar.gz file
before the autotools way is implemented
git-svn-id: http://s3fs.googlecode.com/svn/trunk@204 df820570-a93a-0410-bd06-b72b767a4274
upper case letters.
Research shows that many S3 tools do not support buckets whose
names contain uppercase characters -- s3fs appears to be no
different. However, s3fs allows a bucket of this type to be
mounted even though access to it results in a "Input/output error"
Rather than put support in for these buckets, it's easier to
inform the user of the offending bucket name and die.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@203 df820570-a93a-0410-bd06-b72b767a4274
chregu's code stream
Tested the use_rrs=1 option and confirmed that the files in the
bucket are being tagged as using RRS through Amazon's AWS cockpit
git-svn-id: http://s3fs.googlecode.com/svn/trunk@200 df820570-a93a-0410-bd06-b72b767a4274
of compiling unconditionally at every invocation of
make - actually look at the dependancy
git-svn-id: http://s3fs.googlecode.com/svn/trunk@199 df820570-a93a-0410-bd06-b72b767a4274
Applied supplied patch.
The patch solves this issue by modifying the lookupMimeType function to not only
analyze the last extension for a matching mime type, but analyze the second
to last extension if the last extension did not result in a match.
git-svn-id: http://s3fs.googlecode.com/svn/trunk@198 df820570-a93a-0410-bd06-b72b767a4274
