Fix amazon s3 container handling
See https://github.com/strongloop/loopback-storage-service/issues/16
This commit is contained in:
parent
01befd1c8d
commit
f266024c1b
|
@ -25,6 +25,11 @@ function patchBaseClass(cls) {
|
|||
proto._setProperties = function (details) {
|
||||
// Use an empty object to receive the calculated properties from details
|
||||
var receiver = {};
|
||||
// Pass in some context as non-enumerable properties
|
||||
Object.defineProperties(receiver, {
|
||||
client: {value: this.client},
|
||||
files: {value: this.files}
|
||||
});
|
||||
m1.call(receiver, details);
|
||||
// Apply the calculated properties to this
|
||||
for (var p in receiver) {
|
||||
|
|
|
@ -64,6 +64,7 @@ StorageService.prototype.getContainers = function (cb) {
|
|||
StorageService.prototype.createContainer = function (options, cb) {
|
||||
options = options || {};
|
||||
if ('object' === typeof options && !(options instanceof storage.Container)) {
|
||||
options.Name = options.name; // Amazon expects Name
|
||||
var Container = factory.getProvider(this.provider).storage.Container;
|
||||
options = new Container(this.client, options);
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue