Just wanted to clarify about Tyk Pump: it is quite dumb and does not know anything about API policies, etc. Its the main job is to extract analytics data from Redis and pump it to various sources if it is mongo or elastic search.
Regarding your points:
a) we afraid human mistakes when using GUI to modify API and policy.
b) easier to do CI and CD
Totally get it, and worth mentioning that Dashboard is not just a GUI. It is a separate powerful API, which allows you to configure organization and users. It is similar to Gateway API but has more options and extensions. Actual UI is a thing layer that uses the same API as you would do. This is quite common among our users that they do not use dashboard for its UI, but instead use only dashboard API, and use own dashboards for analytics. By using API, you can ensure that human mistakes are minimized, and CI/CD works flawlessly.
The big bonus of using Dashboard API, is that you can manange multiple Tyk Gateway instances using single API call, and it act as the single source for all truth. When you make changes in the dashboard, it propagates them to all Tyk Gateways, and automatically hot reload them.
Hope it makes sense!
Leonid, Tyk Team