Zaid Albirawi

Hello @jvisker that can definitely be done. You can turn off detailed logging on [gateway level](https://tyk.io/docs/tyk-oss-gateway/configuration/#analytics_configenable_detailed_recording), [globally in Tyk Pump](https://tyk.io/docs/tyk-pump/tyk-pump-configuration/tyk-pump-environment-variables/#omit_detailed_recording) or per [pump](https://tyk.io/docs/tyk-pump/tyk-pump-configuration/tyk-pump-environment-variables/#pumpsmongoomit_detailed_recording). Hope this helps!

Ah gotcha!

I rebased this to master so I can rebase my portal branch off of this and resolve all the changes and have the PR ready to go.

Hello @ESBUINBOO I have run into this issue myself. The way I got around is by creating different values.yaml files and installing different helms. I hope that this idea helps.

@excieve @cherrymu what do you guys think about adding this to allow users to deploy the pump as a service. Maybe we should also make the service ports an array?...

@cherrymu you're right well cross that bridge when we get there. Let's leave the ports array as is for now. We would also have to make the containerPort an array...

@cherrymu you can approve and merge whenever you are happy with this

That's beautiful. I am to go ahead and close this PR.

Sounds good I will close this x2 😆

What the PR is missing: - portal connection string should be a secret :white_check_mark: - bootstrap script should bootstrap portal :white_check_mark: - ~~sqlite3 is not working. Seems to be a...