fa6e9540a8
server: We shouldn't exit the server in lazy init. ( #2548 )
...
Avoid fatalIf instead these are non-critical errors,
continue running the server.
- initializing bucket notifications
- initializing bucket policies.
- migrating bucket policies failure.
Fixes #2547
8 years ago
040af08473
server: Startup message now prints configured ARNs. ( #2653 )
...
Fixes #2628
8 years ago
bccf549463
server: Move all the top level files into cmd folder. ( #2490 )
...
This change brings a change which was done for the 'mc'
package to allow for clean repo and have a cleaner
github drop in experience.
8 years ago
e86dfcf41e
api: Change listen bucket notification to be TopicConfiguration. ( #2447 )
8 years ago
51d7749c3e
Check if eventN is initialized before notifying in Upload web handler ( #2435 )
8 years ago
341171f326
Problem: AWS documentation defines event timestamp as 1970-01-01T00:00:00.000Z ( #2440 )
...
While Minio is using 20160814T124605Z
(See http://docs.aws.amazon.com/AmazonS3/latest/dev/notification-content-structure.html )
Solution: adhere to AWS documentation
8 years ago
064c51162d
api: Add new ListenBucketNotificationHandler. ( #2336 )
...
This API is precursor before implementing `minio lambda` and `mc` continous replication.
This new api is an extention to BucketNofication APIs.
// Request
```
GET /bucket?notificationARN=arn:minio:lambda:us-east-1:10:minio HTTP/1.1
...
...
```
// Response
```
{"Records": ...}
...
...
...
{"Records": ...}
```
8 years ago
Harshavardhana