okv / east-mongo Goto Github PK

The api for mongodb native has changed blowing up east-mongo. Need to either lock down the version of mongodb or upgrade the api usage. I will create a quick pr for the lock down option

error:

the server/replset/mongos options are deprecated, all their options are supported at the top level of the options object [poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,keepAliveInitialDelay,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,checkServerIdentity,validateOptions,appname,auth,user,password,authMechanism,compression,fsync,readPreferenceTags,numberOfRetries,auto_reconnect,minSize] target migrations:

mongodb is set as a peer dependency, but ^4.x.x is not included in this list. It seems to be working fine in our case. Just wandering if this is going to updated any time soon, so we can npm install without --legacy-peer-deps.

Thanks for the adapter.

I tried using the 'dir' option to set the path of my migrations folder and nothing happens. These are the commands i tried.

east --dir .migrations/
east --dir ".migrations/
east --dir '.migrations/'

None of these work. Any idea why?

the current implementation means a separate configuration file per environment, which is kinda anti 12 factor, blah, blah...