[Feature Request] "RECON" feed automatic creation on deployment

[Street3r]

Need a API command to create RECON-feed for takserver as it is deployed. This is needed to have the first mission ready when the users come to the server. Possibly this can be created after first admin is created if there isn't a user id that can be used.

API description from tak.gov:
https://docs.tak.gov/api/takserver#tag/mission-api/operation/createMission

API can also be seen from the takserver with swagger:
https://host/IP:8443/swagger-ui/index.html

Information for the API to create RECON feed:
name: RECON
creatorUid: ?? / first admin?
group: default / tak_default (depends on the group naming)
description: Recon feed for validated information
defaultRole: MISSION_SUBSCRIBER
keywords: #RECON

[Street3r]

You can also do a automatic invitation to users that have not subscribed to the feed. This can be based on user login to server.
https://docs.tak.gov/api/takserver#tag/mission-api/operation/inviteToMission

[benjamsf]

Yes, this would be great.
Thinking the feature a bit further,

1. Could we define like "presets" of different feeds to be automatically created by user decision? Eg. make Rasenmaeher admin capable of examining, selecting, implementing and removing such a "preset"
2. Together with Keycloak based group management, could we also make it so that in such a preset, we could define what user groups & roles to invite for each Feed, in a preset?

A "feed preset" or tak configuration preset (?) should be developed for some user group. A "General" for most usergroups, more specialized ones to well, more specialized use cases.

Relates to the KC group idea of presets.

To be considered

3. Important question: who "owns" this "preset" idea (both feeds, AND preset groups)? a. TAKIntegration or b. core Rasenmaeher via KC?
   Feeds are of course fully a TAK thing. We don't want "fully&only TAK things" to determine what happens in RM, even with TAK. But preset user groups are a thing that is probably shared between products via Rasenmaeher.

3b1. Eg if we had preset called "Company" that creates groups Team1, Team2 and CP, we want to use these groups in the TAK product as well as in the BattleLog product.
3b2. This would say that core Rasenmaeher owns group presets & their management.
3b3. But if and when it is so, how will TAK "Feed Presets" work together with Rasenmaeher "Group Presets"?

Well probably so, that in Rasenmaeher we offer few Group Presets, and in TAKIntegration you can (if you so wish) match a Group Preset (eg. "Company") that Rasenmaeher offers?

TLDR

Make it so that users have to do MINIMAL manual repetitive config - that they have to do anyway, unless we Automatize it. So automating feed creation would be super.

[Street3r]

1./2. For the Recon feed there should be predetermined basic settings. I believe the default role should be subscriber (read/write to feed, but no deleting or altering feed) and if the server admin wants/needs they could change it to read-only and specify who has write privileges.

Problem with different privileges is it is not group based, it is client uid based.
You can automatically add admins on promote or group addition from Rasenmaeher, but the Recon feed must be working at this point and the parameter for which users are given must be predefined in the basic settings which is harder upfront. What if it is a Platoon sized server and everyone should have ability to write to Recon feed. Most likely when the read-only need is there is a bigger organisation and a lot more managing needed from the CP so they could define who has write access and no automation.

https://docs.tak.gov/api/takserver#tag/mission-api/operation/setMissionRole

[benjamsf]

We want probably to spawn X feeds automatically (minimal, but some - some that are about always used) and so support users to do Good Basic Things. Not just "recon" feed so.

Feed names and how they are configured at that automatic deployment are of course just conventions but for making things easy, we probably want some convention

• only conventions UNLESS in the future feed automation relates to (similarily) automatic basic group setup (ref [Epic] [Feature Request] KC Groups & Roles Management into Rasenmaeher UI docker-rasenmaeher-integration#124), though that permission management is based to client uid probably makes that tougher (Just why TAK, why... isn't groups for sane RBAC...)

[Street3r]

Yeah, so like CompanyRECON-feed, Platoon1-feed, Platoon2-feed etc. To accomplish this we need pretty specific organisation maps and it is not too flexible.

These could come from the Organization Hierarchy import but the problem with read-only feeds is that you have to specify what devices get write and it would have to be a specific group and we need group management for that. This could be future feature reguest goal once we get RECON -feed automatic creation and group management working.