Alexander Chernov

@robfig what about introducing an opt-in flag? This way it would be backwards compatible.

Added additional point about vendoring.

> I may be overlooking it, but where's the vendoring point? No idea where it went :| My point was: lets abandon vendoring and go completely with go.mod, as far...

Oh, and by the Data interface I meant something like this: ```go type DataLayerStruct interface { BeginTransaction() error Commit() error Rollback() error GetCookbook(ctx context.Context) cookbook.Cookbook UpdateCookbook(ctx context.Context,cookbook2 cookbook.Cookbook) error }...

No worries :) For the next couple of weeks or so I will be busy with deploying the current version of goiardi to prod, once that's over and we are...

Nope, its not in memory issue. We are running with ``` GOIARDI_PG_SEARCH: true GOIARDI_USE_POSTGRESQL: true ``` also, cluster was not in production so it was not running any other operation...

Turns out its worse than I originally thought. Originally I assumed that the issue is caused by goiardi not releasing heap objects fast enough (I was hammering it after all),...

Sadly its not only that. If I am understanding your correctly, you are talking mostly about the association cookbook->cookbook version. In theory, (since I am working completely on s3/postgresql) such...

I've been able to fix the memory leak (sadly there was a lot of refactoring and the change cannot be merged in to the master branch due to conflicts related...

@ctdk I've created a pull request. **NOTE** that pr should NOT be merged because atm we are - still testing out the implementation - goairdi import/export is broken atm In...