search

AidanTilgner / Onyx-Personal

This is my personal version of the (so far nonexistent) Onyx Systems core microservices. This is the original project and might change over time, but is completely self-hostable. Still very much pre-production though.
1 stars 0 forks source link

Action server and Interpretation server should communicate on what actions they have defined #36

Closed AidanTilgner closed 2 years ago

AidanTilgner commented 2 years ago

Coupling isn't the best in an architecture like this, but in this case it's warranted and I'd say fine. The Interpretation server is in charge of assigning semantic meaning to an action, and so actions will be defined in the Interpretation server, but then they are expected to be executed in the Action server. Therefore, we need a way for the Action server to be able to tell when the Interpretation server has an action that the Action server doesn't, or vice versa. That way updates can be made accordingly and features can be added.

AidanTilgner commented 2 years ago

The Interpretation server will now display which actions are unsupported by the action server in the "actions" section of the portal. This needs to, however, be reciprocated by the action server. Although I don't want to make a client for the Actions server yet, I want to instead output these into a file, where the dev can view the actions that are unsupported, and act accordingly. This will be loaded on server startup, so whenever you make file changes it will be overwritten.

AidanTilgner commented 2 years ago

The action server now logs unsupported actions, and unsupported actions without responses, in storage/metadata. Now a developer can see what actions to work on by looking at either auto-generated file.