MyFavMirrors
/
minio
mirror of https://github.com/minio/minio.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
minio/vendor/vendor.json

399 lines
13 KiB
JSON
Raw Normal View History

Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
"comment": "",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"ignore": "test",
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
"package": [
Implement S3 Gateway to third party cloud storage providers. (#3756) Currently supported backend is Azure Blob Storage. ``` export MINIO_ACCESS_KEY=azureaccountname export MINIO_SECRET_KEY=azureaccountkey minio gateway azure ```
2017-03-16 15:21:58 -04:00
{
"checksumSHA1": "rK3ght7KTtHGdm0V4+U7fv9+tUU=",
"path": "github.com/Azure/azure-sdk-for-go/storage",
"revision": "8e625d1702a32d01cef05a9252198d231c4af113",
"revisionTime": "2017-02-08T01:01:20Z"
},
logrus logger
2015-09-09 23:28:09 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/Sirupsen/logrus",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "32055c351ea8b00b96d70f28db48d9840feaf0ec",
"revisionTime": "2016-07-12T20:17:32-04:00"
logrus logger
2015-09-09 23:28:09 -04:00
},
server: terminal width should fallback to 80x25. (#1895) Some environments might disable access to `/dev/tty`, fall back to '80' in such scenarios. Move to 'cheggaaa/pb' package for better cross platform support on fetching terminal width. Fixes #1891
2016-06-12 22:35:28 -04:00
{
"path": "github.com/cheggaaa/pb",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "73ae1d68fe0bd482ab11913a9828634f795b987f",
"revisionTime": "2016-07-13T13:44:25+03:00"
server: terminal width should fallback to 80x25. (#1895) Some environments might disable access to `/dev/tty`, fall back to '80' in such scenarios. Move to 'cheggaaa/pb' package for better cross platform support on fetching terminal width. Fixes #1891
2016-06-12 22:35:28 -04:00
},
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
{
"checksumSHA1": "/5cvgU+J4l7EhMXTK76KaCAfOuU=",
"path": "github.com/davecgh/go-spew/spew",
"revision": "346938d642f2ec3594ed81d874461961cd0faa76",
"revisionTime": "2016-10-29T20:57:26Z"
},
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
{
"path": "github.com/dgrijalva/jwt-go",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "01aeca54ebda6e0fbfafd0a524d234159c05ec20",
"revisionTime": "2016-07-05T13:30:06-07:00"
},
{
"path": "github.com/dgrijalva/jwt-go/request",
"revision": "01aeca54ebda6e0fbfafd0a524d234159c05ec20",
"revisionTime": "2016-07-05T13:30:06-07:00"
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/dustin/go-humanize",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "fef948f2d241bd1fd0631108ecc2c9553bae60bf",
"revisionTime": "2016-06-23T09:40:21+08:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
{
"checksumSHA1": "y2Kh4iPlgCPXSGTCcFpzePYdzzg=",
"path": "github.com/eapache/go-resiliency/breaker",
"revision": "b86b1ec0dd4209a588dc1285cdd471e73525c0b3",
"revisionTime": "2016-01-04T19:15:39Z"
},
{
"checksumSHA1": "WHl96RVZlOOdF4Lb1OOadMpw8ls=",
"path": "github.com/eapache/go-xerial-snappy",
"revision": "bb955e01b9346ac19dc29eb16586c90ded99a98c",
"revisionTime": "2016-06-09T14:24:08Z"
},
{
"checksumSHA1": "oCCs6kDanizatplM5e/hX76busE=",
"path": "github.com/eapache/queue",
"revision": "44cc805cf13205b55f69e14bcb69867d1ae92f98",
"revisionTime": "2016-08-05T00:47:13Z"
},
UI: vendorize github.com/elazarl/go-bindata-assetfs which is needed by ui-assets.go
2016-02-04 06:20:34 -05:00
{
"path": "github.com/elazarl/go-bindata-assetfs",
ui-assets: Integrate UI assets.
2016-02-04 19:00:52 -05:00
"revision": "57eb5e1fc594ad4b0b1dbea7b286d299e0cb43c2",
"revisionTime": "2015-12-24T06:54:52+02:00"
UI: vendorize github.com/elazarl/go-bindata-assetfs which is needed by ui-assets.go
2016-02-04 06:20:34 -05:00
},
Add WebUI assetfs initial version
2015-09-25 03:37:28 -04:00
{
Make minio server compile on OpenBSD, NetBSD, Solaris (#3719)
2017-02-09 01:27:35 -05:00
"checksumSHA1": "XEBl9iQQvfXNlwCSzyAOCqAlYEA=",
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/fatih/color",
Make minio server compile on OpenBSD, NetBSD, Solaris (#3719)
2017-02-09 01:27:35 -05:00
"revision": "42c364ba490082e4815b5222728711b3440603eb",
"revisionTime": "2017-01-13T15:16:12Z"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
Vendor upstream redis library instead of our fork. (#3913) We forked the upstream to address a build issue on go 1.6 - that is long done and we don't need to manage our forks anymore.
2017-03-16 11:22:47 -04:00
{
"checksumSHA1": "2UmMbNHc8FBr98mJFN1k8ISOIHk=",
"path": "github.com/garyburd/redigo/internal",
"revision": "0d253a66e6e1349f4581d6d2b300ee434ee2da9f",
"revisionTime": "2017-02-16T21:49:44Z"
},
{
"checksumSHA1": "81OSg/NapmTaRpSS+oYsPVE0b1Y=",
"path": "github.com/garyburd/redigo/redis",
"revision": "0d253a66e6e1349f4581d6d2b300ee434ee2da9f",
"revisionTime": "2017-02-16T21:49:44Z"
},
Add support for MySQL notifications (fixes #3818) (#3907) As a new configuration parameter is added, configuration version is bumped up from 14 to 15. The MySQL target's behaviour is identical to the PostgreSQL: rows are deleted from the MySQL table on delete-object events, and are created/updated on create/over-write events.
2017-03-17 12:29:17 -04:00
{
"checksumSHA1": "QD6LqgLz2JMxXqns8TaxtK9AuHs=",
"path": "github.com/go-sql-driver/mysql",
"revision": "2e00b5cd70399450106cec6431c2e2ce3cae5034",
"revisionTime": "2016-12-24T12:10:19Z"
},
nats: Add support of NATS.io Streaming server (#3494)
2017-01-11 19:41:05 -05:00
{
"checksumSHA1": "3yco0089CSJ4qbyUccpbDC2+dPg=",
"path": "github.com/gogo/protobuf/gogoproto",
"revision": "84af2615df1ba1d35cc975ba94b64ee67d6c196e",
"revisionTime": "2016-12-20T17:02:12Z"
},
{
"checksumSHA1": "6ZxSmrIx3Jd15aou16oG0HPylP4=",
"path": "github.com/gogo/protobuf/proto",
"revision": "84af2615df1ba1d35cc975ba94b64ee67d6c196e",
"revisionTime": "2016-12-20T17:02:12Z"
},
{
"checksumSHA1": "EaY86bsi1nucvO0/UKvp/A72aC8=",
"path": "github.com/gogo/protobuf/protoc-gen-gogo/descriptor",
"revision": "84af2615df1ba1d35cc975ba94b64ee67d6c196e",
"revisionTime": "2016-12-20T17:02:12Z"
},
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"checksumSHA1": "W+E/2xXcE1GmJ0Qb784ald0Fn6I=",
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
"path": "github.com/golang/snappy",
"revision": "d9eb7a3d35ec988b8585d4a0068e462c27d28380",
"revisionTime": "2016-05-29T05:00:41Z"
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/gorilla/context",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "aed02d124ae4a0e94fea4541c8effd05bf0c8296",
"revisionTime": "2016-05-25T13:33:19-07:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
browser-assets: serve asset files with compression.
2016-03-03 21:15:56 -05:00
{
"path": "github.com/gorilla/handlers",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "66e6c6f01d8da976ee113437745ca029c2b585a6",
"revisionTime": "2016-04-10T11:53:17-07:00"
browser-assets: serve asset files with compression.
2016-03-03 21:15:56 -05:00
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/gorilla/mux",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "9fa818a44c2bf1396a17f9d5a3c0f6dd39d2ff8e",
"revisionTime": "2016-06-05T16:35:21-07:00"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
{
"path": "github.com/gorilla/rpc/v2",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
},
{
WebUI: move from rpc/v2/json to rpc/v2/json2 which has better error response structure.
2016-02-11 13:11:43 -05:00
"path": "github.com/gorilla/rpc/v2/json2",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "bd3317b8f6704b1b40e4e705ec9e987a535cd5d3",
"revisionTime": "2016-05-16T23:23:31-07:00"
Bring in the list APIs implemented by Bala <bala@minio.io>
2016-01-23 22:44:32 -05:00
},
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
{
"path": "github.com/hashicorp/go-version",
"revision": "7e3c02b30806fa5779d3bdfc152ce4c6f40e7b38",
"revisionTime": "2016-01-19T13:13:26-08:00"
},
cpu: Remove pkg/cpu in favor of better klauspost/cpuid. Fixes #1128
2016-02-15 15:45:02 -05:00
{
"path": "github.com/klauspost/cpuid",
"revision": "349c675778172472f5e8f3a3e0fe187e302e5a10",
"revisionTime": "2016-01-06T11:44:51+01:00"
},
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
{
"checksumSHA1": "BM6ZlNJmtKy3GBoWwg2X55gnZ4A=",
"path": "github.com/klauspost/crc32",
"revision": "cb6bfca970f6908083f26f39a79009d608efd5cd",
"revisionTime": "2016-10-16T15:41:25Z"
},
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"checksumSHA1": "Pzd1bfm8Yj1radncaohNZu+UT1I=",
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
"path": "github.com/klauspost/reedsolomon",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"revision": "d0a56f72c0d40a6cdde43a1575ad9686a0098b70",
"revisionTime": "2016-10-28T07:13:20Z"
Implement XL layer - preliminary work.
2016-03-28 00:52:38 -04:00
},
Add PostgreSQL notifier (#2739) (#2824) * The user is required to specify a table name and database connection information in the configuration file. * INSERTs and DELETEs are done via prepared statements for speed. * Assumes a table structure, and requires PostgreSQL 9.5 or above due to the use of UPSERT. * Creates the table if it does not exist with the given table name using a query like: CREATE TABLE myminio ( key varchar PRIMARY KEY, value JSONB ); * Vendors some required libraries.
2016-10-03 20:29:55 -04:00
{
"checksumSHA1": "dNYxHiBLalTqluak2/Z8c3RsSEM=",
"path": "github.com/lib/pq",
"revision": "50761b0867bd1d9d069276790bcd4a3bccf2324a",
"revisionTime": "2016-08-31T22:25:20Z"
},
{
"checksumSHA1": "xppHi82MLqVx1eyQmbhTesAEjx8=",
"path": "github.com/lib/pq/oid",
"revision": "50761b0867bd1d9d069276790bcd4a3bccf2324a",
"revisionTime": "2016-08-31T22:25:20Z"
},
vendor: Update to new upstream changes from fatih/color Brings in changes like support for Solaris/FreeBSD.
2016-02-23 17:56:47 -05:00
{
"path": "github.com/mattn/go-colorable",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "9056b7a9f2d1f2d96498d6d146acd1f9d5ed3d59",
"revisionTime": "2016-06-03T00:08:27+09:00"
vendor: Update to new upstream changes from fatih/color Brings in changes like support for Solaris/FreeBSD.
2016-02-23 17:56:47 -05:00
},
First time mode for controller - Upon first time invocation ``minio controller`` would create access keys and secret id - Upon request passing 'keys' arg ``minio controller`` would provide the keys - Add colorized notification
2015-10-04 19:31:07 -04:00
{
Make minio server compile on OpenBSD, NetBSD, Solaris (#3719)
2017-02-09 01:27:35 -05:00
"checksumSHA1": "xZuhljnmBysJPta/lMyYmJdujCg=",
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/mattn/go-isatty",
Make minio server compile on OpenBSD, NetBSD, Solaris (#3719)
2017-02-09 01:27:35 -05:00
"revision": "30a891c33c7cde7b02a981314b4228ec99380cca",
"revisionTime": "2016-11-23T14:36:37Z"
First time mode for controller - Upon first time invocation ``minio controller`` would create access keys and secret id - Upon request passing 'keys' arg ``minio controller`` would provide the keys - Add colorized notification
2015-10-04 19:31:07 -04:00
},
Move to blake2b-simd due to perf problems in golang.org/x/crypto Ref https://github.com/golang/go/issues/18563
2017-01-24 21:07:31 -05:00
{
"checksumSHA1": "4gphCNVXIjp5ytz3+S3SD3Dp948=",
"path": "github.com/minio/blake2b-simd",
"revision": "3f5f724cb5b182a5c278d6d3d55b40e7f8c2efb4",
"revisionTime": "2016-07-23T06:10:19Z"
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Implement S3 Gateway to third party cloud storage providers. (#3756) Currently supported backend is Azure Blob Storage. ``` export MINIO_ACCESS_KEY=azureaccountname export MINIO_SECRET_KEY=azureaccountkey minio gateway azure ```
2017-03-16 15:21:58 -04:00
"checksumSHA1": "fUWokilZyc1QDKnIgCDJE8n1S9U=",
Migrate this project to minio micro services code
2015-10-16 14:26:01 -04:00
"path": "github.com/minio/cli",
Implement S3 Gateway to third party cloud storage providers. (#3756) Currently supported backend is Azure Blob Storage. ``` export MINIO_ACCESS_KEY=azureaccountname export MINIO_SECRET_KEY=azureaccountkey minio gateway azure ```
2017-03-16 15:21:58 -04:00
"revision": "b8ae5507c0ceceecc22d5dbd386b58fbd4fdce72",
"revisionTime": "2017-02-27T07:32:28Z"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
},
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
{
Adopt dsync interface changes and major cleanup on RPC server/client. * Rename GenericArgs to AuthRPCArgs * Rename GenericReply to AuthRPCReply * Remove authConfig.loginMethod and add authConfig.ServiceName * Rename loginServer to AuthRPCServer * Rename RPCLoginArgs to LoginRPCArgs * Rename RPCLoginReply to LoginRPCReply * Version and RequestTime are added to LoginRPCArgs and verified by server side, not client side. * Fix data race in lockMaintainence loop.
2016-12-23 10:12:19 -05:00
"checksumSHA1": "NBGyq2+iTtJvJ+ElG4FzHLe1WSY=",
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
"path": "github.com/minio/dsync",
Adopt dsync interface changes and major cleanup on RPC server/client. * Rename GenericArgs to AuthRPCArgs * Rename GenericReply to AuthRPCReply * Remove authConfig.loginMethod and add authConfig.ServiceName * Rename loginServer to AuthRPCServer * Rename RPCLoginArgs to LoginRPCArgs * Rename RPCLoginReply to LoginRPCReply * Version and RequestTime are added to LoginRPCArgs and verified by server side, not client side. * Fix data race in lockMaintainence loop.
2016-12-23 10:12:19 -05:00
"revision": "9cafd4d729eb71b31ef7851a8c8f6ceb855d0915",
"revisionTime": "2016-12-23T07:07:24Z"
distribute: Make server work with multiple remote disks This change initializes rpc servers associated with disks that are local. It makes object layer initialization on demand, namely on the first request to the object layer. Also adds lock RPC service vendorized minio/dsync
2016-07-31 17:11:14 -04:00
},
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
{
"path": "github.com/minio/go-homedir",
vendor update for go-homedir
2016-02-18 02:32:41 -05:00
"revision": "0b1069c753c94b3633cc06a1995252dbcc27c7a6",
"revisionTime": "2016-02-15T17:25:11+05:30"
rewrite minio runtime checks
2016-02-15 07:26:56 -05:00
},
console: Fix console color printing on windows. Print colored accessKeyID and secretAccessKey are unreadable on windows on command prompts and powershell. Use the console package from minio client.
2016-03-04 04:50:59 -05:00
{
"path": "github.com/minio/mc/pkg/console",
"revision": "db6b4f13442b26995f04b3b2b31b006cae7786e6",
"revisionTime": "2016-02-29T08:42:30-08:00"
},
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
{
web: add method to get all policies for given bucket name. (#2756) Refer #1858
2016-09-23 02:06:45 -04:00
"checksumSHA1": "qTxOBp3GVxCC70ykb7Hxg6UgWwA=",
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
"path": "github.com/minio/minio-go/pkg/policy",
web: add method to get all policies for given bucket name. (#2756) Refer #1858
2016-09-23 02:06:45 -04:00
"revision": "40505f5d08c721dfe5a6450fbdef3bcd6567aa97",
"revisionTime": "2016-09-04T08:12:15Z"
web: add handlers for set/get bucket policy. (#2486) Refer #1858
2016-08-30 13:04:50 -04:00
},
admin: Fix wrong vendorized location for s3signer and s3utils.
2016-12-20 18:18:37 -05:00
{
"checksumSHA1": "l95EyvF0yFAItXsXYqsZ6g7yGy4=",
"path": "github.com/minio/minio-go/pkg/s3signer",
"revision": "d02caa62b9e1034f93a82d41da806651a666c5a3",
"revisionTime": "2016-12-14T00:10:05Z"
},
{
"checksumSHA1": "bPvxFS1qu6W9lOqdt8aEfS5Sids=",
"path": "github.com/minio/minio-go/pkg/s3utils",
"revision": "532b920ff28900244a2ef7d07468003df36fe7c5",
"revisionTime": "2016-12-20T20:43:13Z"
},
api/bucketPolicy: Use minio-go/pkg/set and fix bucket policy regression. (#2506) Current master has a regression 'mc policy <policy-type> alias/bucket/prefix' does not work anymore, due to the way new minio-go changes do json marshalling. This led to a regression on server side when a ``prefix`` is provided policy is rejected as malformed from th server which is not the case with AWS S3. This patch uses the new ``minio-go/pkg/set`` package to address the unmarshalling problems. Fixes #2503
2016-08-20 06:16:38 -04:00
{
Add extensive endpoints validation (#4019)
2017-04-11 18:44:27 -04:00
"checksumSHA1": "maUy+dbN6VfTTnfErrAW2lLit1w=",
api/bucketPolicy: Use minio-go/pkg/set and fix bucket policy regression. (#2506) Current master has a regression 'mc policy <policy-type> alias/bucket/prefix' does not work anymore, due to the way new minio-go changes do json marshalling. This led to a regression on server side when a ``prefix`` is provided policy is rejected as malformed from th server which is not the case with AWS S3. This patch uses the new ``minio-go/pkg/set`` package to address the unmarshalling problems. Fixes #2503
2016-08-20 06:16:38 -04:00
"path": "github.com/minio/minio-go/pkg/set",
Add extensive endpoints validation (#4019)
2017-04-11 18:44:27 -04:00
"revision": "7a3619e41885dcbcfafee193c10eb80530c2be53",
"revisionTime": "2017-02-17T20:03:45Z"
api/bucketPolicy: Use minio-go/pkg/set and fix bucket policy regression. (#2506) Current master has a regression 'mc policy <policy-type> alias/bucket/prefix' does not work anymore, due to the way new minio-go changes do json marshalling. This led to a regression on server side when a ``prefix`` is provided policy is rejected as malformed from th server which is not the case with AWS S3. This patch uses the new ``minio-go/pkg/set`` package to address the unmarshalling problems. Fixes #2503
2016-08-20 06:16:38 -04:00
},
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
{
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"checksumSHA1": "URVle4qtadmW9w9BulDRHY3kxnA=",
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
"path": "github.com/minio/sha256-simd",
vendorize deps for snappy, blake2b and sha256 (#3476) Bring in new optimization and portability changes. Fixes https://github.com/minio/minio-go/issues/578
2016-12-19 22:32:55 -05:00
"revision": "e82e73b775766b9011503e80e6772fc32b9afc5b",
"revisionTime": "2016-12-19T23:17:30Z"
Switched to faster minio/sha256-simd implementation (#2320)
2016-07-28 17:44:37 -04:00
},
nats: Add support of NATS.io Streaming server (#3494)
2017-01-11 19:41:05 -05:00
{
"checksumSHA1": "zvQr4zOz1/g/Fui6co0sctxrJ28=",
"path": "github.com/nats-io/go-nats",
"revision": "6b6bf392d34d01f57cc563ae123f00c13778bd57",
"revisionTime": "2016-11-20T20:21:26Z"
},
{
"checksumSHA1": "8Z7LvciW35L7fbH0IaSoBMae+3o=",
"path": "github.com/nats-io/go-nats-streaming",
"revision": "077898146bfbb849a620202e7e5eaaf707492206",
"revisionTime": "2016-12-16T19:10:29Z"
},
{
"checksumSHA1": "16sV1MZ45lYmv2tXfKHCz+ZLvyY=",
"path": "github.com/nats-io/go-nats-streaming/pb",
"revision": "077898146bfbb849a620202e7e5eaaf707492206",
"revisionTime": "2016-12-16T19:10:29Z"
},
{
"checksumSHA1": "Q2c9uTEIGhSIddv5pntYdFNtUdk=",
"path": "github.com/nats-io/go-nats/encoders/builtin",
"revision": "6b6bf392d34d01f57cc563ae123f00c13778bd57",
"revisionTime": "2016-11-20T20:21:26Z"
},
{
"checksumSHA1": "LhbIA/oMWpscEPPK9Wrx5GLcz44=",
"path": "github.com/nats-io/go-nats/util",
"revision": "6b6bf392d34d01f57cc563ae123f00c13778bd57",
"revisionTime": "2016-11-20T20:21:26Z"
},
Add NATS notifier (#2795)
2016-09-30 02:42:10 -04:00
{
"checksumSHA1": "Nj7vQ2GlvJiPP7sqJX5AurrDSD4=",
"path": "github.com/nats-io/nats",
"revision": "70b70be17b77e8da86b6a3bcfe94fb22718a8dd0",
"revisionTime": "2016-09-16T18:17:35Z"
},
{
"checksumSHA1": "qAIuHdtQrDi2fFmpaP1dZLbgpGc=",
"path": "github.com/nats-io/nats/encoders/builtin",
"revision": "70b70be17b77e8da86b6a3bcfe94fb22718a8dd0",
"revisionTime": "2016-09-16T18:17:35Z"
},
{
"checksumSHA1": "i8Yom1KrpDKwjlGH/gpJGAQmo68=",
"path": "github.com/nats-io/nuid",
"revision": "289cccf02c178dc782430d534e3c1f5b72af807f",
"revisionTime": "2016-09-27T04:49:45Z"
},
server: Enable server profiling as needed. (#1565)
2016-05-09 19:18:56 -04:00
{
"path": "github.com/pkg/profile",
vendor changes to pkg/profile (#1671)
2016-05-18 12:22:06 -04:00
"revision": "c78aac22bd43883fd2817833b982153dcac17b3b",
"revisionTime": "2016-05-18T16:56:57+10:00"
server: Enable server profiling as needed. (#1565)
2016-05-09 19:18:56 -04:00
},
Enable controller to have CORS
2015-08-31 04:47:05 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "github.com/rs/cors",
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
"revision": "a62a804a8a009876ca59105f7899938a1349f4b3",
"revisionTime": "2016-06-18T04:49:35+05:30"
},
{
"path": "github.com/rs/xhandler",
"revision": "ed27b6fd65218132ee50cd95f38474a3d8a2cd12",
"revisionTime": "2016-06-18T12:32:21-07:00"
Enable controller to have CORS
2015-08-31 04:47:05 -04:00
},
backend/fs: Refactor multipart upload This patch modifies multipart upload related functions as below * New multipart upload call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.uploadid * Put object part call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.PART_NUMBER.MD5SUM_STRING * Abort multipart call removes all files matching EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.* * Complete multipart call does 1. creates a staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete.TEMP_NAME then renames to EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete 2. rename staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete to EXPORT_DIR/BUCKET/PATH/TO/OBJECT
2016-03-28 12:52:09 -04:00
{
"checksumSHA1": "u0hXGADM3JDza8YjgiyNJpAJk8g=",
"path": "github.com/skyrings/skyring-common/tools/uuid",
"revision": "762fd2bfc12e766d90478d638255981ab1966a3d",
"revisionTime": "2016-03-24T19:44:43+05:30"
},
api: Implement bucket notification. (#2271) * Implement basic S3 notifications through queues Supports multiple queues and three basic queue types: 1. NilQueue -- messages don't get sent anywhere 2. LogQueue -- messages get logged 3. AmqpQueue -- messages are sent to an AMQP queue * api: Implement bucket notification. Supports two different queue types - AMQP - ElasticSearch. * Add support for redis
2016-07-24 01:51:12 -04:00
{
"checksumSHA1": "rKV8YLkXpeNG1Oix8hlYqVsEFb4=",
"path": "github.com/streadway/amqp",
"revision": "2e25825abdbd7752ff08b270d313b93519a0a232",
"revisionTime": "2016-03-11T21:55:03Z"
},
performance: gjson parsing for readXLMeta, listParts, getObjectInfo. (#2631) - Using gjson for constructing xlMetaV1{} in realXLMeta. - Test for parsing constructing xlMetaV1{} using gjson. - Changes made since benchmarks showed 30-40% improvement in speed. - Follow up comments in issue https://github.com/minio/minio/issues/2208 for more details. - gjson parsing of parts from xl.json for listParts. - gjson parsing of statInfo from xl.json for getObjectInfo. - Vendorizing gjson dependency.
2016-09-09 01:38:18 -04:00
{
config: Check for duplicated entries in all scopes (#3872) Validate Minio config by checking if there is double json key in any scope level. The returned error contains the json path to the duplicated key.
2017-03-15 19:30:34 -04:00
"checksumSHA1": "k/Xh0p5L7+tBCXAL2dOCwUf9J3Y=",
performance: gjson parsing for readXLMeta, listParts, getObjectInfo. (#2631) - Using gjson for constructing xlMetaV1{} in realXLMeta. - Test for parsing constructing xlMetaV1{} using gjson. - Changes made since benchmarks showed 30-40% improvement in speed. - Follow up comments in issue https://github.com/minio/minio/issues/2208 for more details. - gjson parsing of parts from xl.json for listParts. - gjson parsing of statInfo from xl.json for getObjectInfo. - Vendorizing gjson dependency.
2016-09-09 01:38:18 -04:00
"path": "github.com/tidwall/gjson",
config: Check for duplicated entries in all scopes (#3872) Validate Minio config by checking if there is double json key in any scope level. The returned error contains the json path to the duplicated key.
2017-03-15 19:30:34 -04:00
"revision": "09d1c5c5bc64e094394dfe2150220d906c55ac37",
"revisionTime": "2017-02-05T16:10:42Z"
performance: gjson parsing for readXLMeta, listParts, getObjectInfo. (#2631) - Using gjson for constructing xlMetaV1{} in realXLMeta. - Test for parsing constructing xlMetaV1{} using gjson. - Changes made since benchmarks showed 30-40% improvement in speed. - Follow up comments in issue https://github.com/minio/minio/issues/2208 for more details. - gjson parsing of parts from xl.json for listParts. - gjson parsing of statInfo from xl.json for getObjectInfo. - Vendorizing gjson dependency.
2016-09-09 01:38:18 -04:00
},
{
"checksumSHA1": "qmePMXEDYGwkAfT9QvtMC58JN/E=",
"path": "github.com/tidwall/match",
"revision": "173748da739a410c5b0b813b956f89ff94730b4c",
"revisionTime": "2016-08-30T17:39:30Z"
},
admin/info: Add HTTPStats value as part of serverInfo() struct. (#4049) Remove our counter implementation instead use atomic external package which supports more types and methods.
2017-04-07 02:08:33 -04:00
{
"checksumSHA1": "6NS7FWJl1FobB+Xfe4SzBGD+75g=",
"path": "go.uber.org/atomic",
"revision": "3b8db5e93c4c02efbc313e17b2e796b0914a01fb",
"revisionTime": "2016-12-15T19:56:52Z"
},
jwt: Add JWT support for minio server. Please read JWT.md before using this feature.
2016-01-21 19:28:15 -05:00
{
"path": "golang.org/x/crypto/bcrypt",
"revision": "7b85b097bf7527677d54d3220065e966a0e3b613",
"revisionTime": "2015-11-30T17:07:01-05:00"
},
{
"path": "golang.org/x/crypto/blowfish",
"revision": "7b85b097bf7527677d54d3220065e966a0e3b613",
"revisionTime": "2015-11-30T17:07:01-05:00"
},
vendorize: update all vendorized packages. (#2206) Bring in new changes from upstream for all the packages. Important ones include - gorilla/mux - logrus - jwt
2016-07-14 17:59:20 -04:00
{
"path": "golang.org/x/net/context",
"revision": "a728288923b47049b2ce791836767ffbe964a5bd",
"revisionTime": "2016-07-07T15:24:52-07:00"
},
Add `access` format support for Elasticsearch notification target (#4006) This change adds `access` format support for notifications to a Elasticsearch server, and it refactors `namespace` format support. In the case of `access` format, for each event in Minio, a JSON document is inserted into Elasticsearch with its timestamp set to the event's timestamp, and with the ID generated automatically by elasticsearch. No events are modified or deleted in this mode. In the case of `namespace` format, for each event in Minio, a JSON document is keyed together by the bucket and object name is updated in Elasticsearch. In the case of an object being created or over-written in Minio, a new document or an existing document is inserted into the Elasticsearch index. If an object is deleted in Minio, the corresponding document is deleted from the Elasticsearch index. Additionally, this change upgrades Elasticsearch support to the 5.x series. This is a breaking change, and users of previous elasticsearch versions should upgrade. Also updates documentation on Elasticsearch notification target usage and has a link to an elasticsearch upgrade guide. This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
{
"checksumSHA1": "WHc3uByvGaMcnSoI21fhzYgbOgg=",
"path": "golang.org/x/net/context/ctxhttp",
"revision": "f2499483f923065a842d38eb4c7f1927e6fc6e6d",
"revisionTime": "2017-01-14T04:22:49Z"
},
Add support for Kafka as a notifications target (#2869) (#3439)
2016-12-15 11:23:48 -05:00
{
"checksumSHA1": "p36nkSZUaOs/7Wtcy/FduBLgm8g=",
"path": "gopkg.in/Shopify/sarama.v1",
"revision": "bd61cae2be85fa6ff40eb23dcdd24567967ac2ae",
"revisionTime": "2016-08-30T13:25:53Z"
},
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
{
Migrate to new govendor
2015-10-11 01:28:56 -04:00
"path": "gopkg.in/check.v1",
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
"revision": "11d3bc7aa68e238947792f30573146a3231fc0f1",
"revisionTime": "2015-07-29T10:04:31+02:00"
api: Implement bucket notification. (#2271) * Implement basic S3 notifications through queues Supports multiple queues and three basic queue types: 1. NilQueue -- messages don't get sent anywhere 2. LogQueue -- messages get logged 3. AmqpQueue -- messages are sent to an AMQP queue * api: Implement bucket notification. Supports two different queue types - AMQP - ElasticSearch. * Add support for redis
2016-07-24 01:51:12 -04:00
},
{
"checksumSHA1": "lLdKOn9RPtFoTtPUNq5+sIInAiE=",
"path": "gopkg.in/olivere/elastic.v3/backoff",
"revision": "f7ae701daf3abe5dfb99f57b3f47738ec93c9c26",
"revisionTime": "2016-07-16T10:42:39Z"
},
{
"checksumSHA1": "XQg6xG6l15Ke43KolthYYnVDCYo=",
"path": "gopkg.in/olivere/elastic.v3/uritemplates",
"revision": "f7ae701daf3abe5dfb99f57b3f47738ec93c9c26",
"revisionTime": "2016-07-16T10:42:39Z"
quick: Add yaml format support (#3833) quick Save() and Load() infers config file's format from file name extension.
2017-03-03 13:22:09 -05:00
},
Add `access` format support for Elasticsearch notification target (#4006) This change adds `access` format support for notifications to a Elasticsearch server, and it refactors `namespace` format support. In the case of `access` format, for each event in Minio, a JSON document is inserted into Elasticsearch with its timestamp set to the event's timestamp, and with the ID generated automatically by elasticsearch. No events are modified or deleted in this mode. In the case of `namespace` format, for each event in Minio, a JSON document is keyed together by the bucket and object name is updated in Elasticsearch. In the case of an object being created or over-written in Minio, a new document or an existing document is inserted into the Elasticsearch index. If an object is deleted in Minio, the corresponding document is deleted from the Elasticsearch index. Additionally, this change upgrades Elasticsearch support to the 5.x series. This is a breaking change, and users of previous elasticsearch versions should upgrade. Also updates documentation on Elasticsearch notification target usage and has a link to an elasticsearch upgrade guide. This is the last patch that finally resolves #3928.
2017-03-31 17:11:27 -04:00
{
"checksumSHA1": "ji4KugVW5dIfKLoFr1fE+3mT90A=",
"path": "gopkg.in/olivere/elastic.v5",
"revision": "cf4e58efdcee2e8e7c18dad44d51ed166fb256c2",
"revisionTime": "2017-03-26T10:11:08Z"
},
{
"checksumSHA1": "pCApZfp2CeDnWbNVsyzNO62ZUXA=",
"path": "gopkg.in/olivere/elastic.v5/uritemplates",
"revision": "cf4e58efdcee2e8e7c18dad44d51ed166fb256c2",
"revisionTime": "2017-03-26T10:11:08Z"
},
quick: Add yaml format support (#3833) quick Save() and Load() infers config file's format from file name extension.
2017-03-03 13:22:09 -05:00
{
"checksumSHA1": "12GqsW8PiRPnezDDy0v4brZrndM=",
"path": "gopkg.in/yaml.v2",
"revision": "a5b47d31c556af34a302ce5d659e6fea44d90de0",
"revisionTime": "2016-09-28T15:37:09Z"
Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.
2015-08-12 22:24:31 -04:00
}
backend/fs: Refactor multipart upload This patch modifies multipart upload related functions as below * New multipart upload call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.uploadid * Put object part call creates file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.PART_NUMBER.MD5SUM_STRING * Abort multipart call removes all files matching EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.* * Complete multipart call does 1. creates a staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete.TEMP_NAME then renames to EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete 2. rename staging file EXPORT_DIR/.minio/BUCKET/PATH/TO/OBJECT/UPLOAD_ID.complete to EXPORT_DIR/BUCKET/PATH/TO/OBJECT
2016-03-28 12:52:09 -04:00
],
"rootPath": "github.com/minio/minio"
Migrate to new govendor
2015-10-11 01:28:56 -04:00
}