Open framitdavid opened 7 months ago
Sikkert lurt å avgrense denne til broker i første omgang, og så at vi lager egen for correspondance?!
Sikkert lurt å avgrense denne til broker i første omgang, og så at vi lager egen for correspondance?! @leogasnier det er nok lurt å begrense det i første omgang, så kan vi se på correspondance når det er mer klart? En annen fordel med å ta det stegvis er at vi kan innhente litt tilbakemeldinger fra brukere.
There has been a request from the "Team Melding og Formidling" to develop an interface for configuring the usage of the messaging service via Studio. The configuration will be done through API endpoints to the messaging service; hence, it will not be stored in files in Gitea like our apps-config. I envision this as an isolated package/module within Studio.
Note: Those who will configure this service are service owners, and therefore, it is logical to have access to this type of configuration in Studio. HOWEVER, we mustn't directly integrate this concept into app development because it may not necessarily correlate. What may be relevant is creating a component that service owners can incorporate into their app to enable document downloads from the message service from the apps.
This is an epic that should contain a list of issues that need to be addressed before we can consider the implementation of messaging service configuration complete. There are two task lists in this epic: one for minimum support and one for full support. The reason for dividing it into two lists is to more easily assess what should be done as part 1 and part 2, considering both time and available resources for implementation.