You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I went through some recent changes and found that the osctrl-api is in a bad position, where no components are using it. osctrl-admin and osctrl-cli are calling database directly. Is there any plan to reduce the code duplication and make sure all the API requests would go through the osctrl-api? It also reduces the risk for direct access to the database.
Also, for organizing the code, I would suggest that we move all the binary main.go to /cmd/osctrl-components and keep only one go.mod file. It helps us find all implementation and references.
The text was updated successfully, but these errors were encountered:
It seems that osctrl-api is broken after this change: #507
I got the following error when calling
QueriesRunHandler
I went through some recent changes and found that the osctrl-api is in a bad position, where no components are using it. osctrl-admin and osctrl-cli are calling database directly. Is there any plan to reduce the code duplication and make sure all the API requests would go through the osctrl-api? It also reduces the risk for direct access to the database.
Also, for organizing the code, I would suggest that we move all the binary main.go to
/cmd/osctrl-components
and keep only one go.mod file. It helps us find all implementation and references.The text was updated successfully, but these errors were encountered: