osher

I think I had to move to `[email protected]` and I was able to continue working but - I'm not sure my oas-mocker is on hold atm since I changed workplace...

Let me add a little more information. The keys & certificates were created using this procedure: https://docs.mongodb.com/manual/appendix/security/appendixA-openssl-ca/ The Mongo DB launched successfully with the PEM, and I have successfully connected...

If I change the `command` in my docker-compose to `sleep 1000000` I can `run -it .. sh` and from there - I successfully connect to the DB using the same...

@dozoisch - thanks. I just made it work and came to share my results. I made it work with the following work-around: in docker-compose: ``` fn-mongo-express-web: container_name: fn-mongo-express-web image: mongo-express...

@klubi - I got the image from docker by simply running `mongo-express`. I even tried with `mongo-express:latest` - however, that was few weaks ago. In a few days I'll have...

sorry I disappeared... the project ended up using a different config engine, so the thread lost priority. I hear all the inputs here, and it makes me want to do...

@vinzscam should the fix be visible in nightly builds?

works for me after `yarn backstage-cli versions:bump` 🚀 😄

I committed tests I started to add - I have a problem with the last case: ``` when provided with a done(err,ctx) callback and the pipe flow succeeds √ should...

I hope I found the cause - `Pipeworks#siphon` does not pass the `faultPipe`. https://github.com/kevinswiber/pipeworks/pull/10