Application Call Stack

Here are the .go files that get called when an API Call is made.

I am taking the example of creating a Definition here and the call stack looks like this:

^{github.com/onap/multicloud-k8s/src/k8splugin/internal/db.(*MongoStore).Create /home/ad_kkkamine/dev/repos/onap/multicloud/k8s/src/k8splugin/internal/db/mongo.go:167 github.com/onap/multicloud-k8s/src/k8splugin/internal/rb.(*DefinitionClient).Create /home/ad_kkkamine/dev/repos/onap/multicloud/k8s/src/k8splugin/internal/rb/definition.go:99 github.com/onap/multicloud-k8s/src/k8splugin/api.rbDefinitionHandler.createHandler /home/ad_kkkamine/dev/repos/onap/multicloud/k8s/src/k8splugin/api/defhandler.go:64}

In general, the flow is Handler → Implemetation → Database

The current logging system just propagates any errors back up without context and it also does not print the error on stdout in a structured format.