feat: WPB-24983 Add On-Prem reference

[MarianKijewski]

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

In general missing information of what's required to have apps in Wire teams. On top of that the process includes additional steps for On-Premise.

Solutions

• Mention all the requirements with the expected resolution before readers go though the process of creating apps.
• apiToken for custom domains

Notes

Currently there's no documentation for migrating to MLS, and no way for Cloud teams to enable feature flag themselves. Both of these scenarios lead to raising a ticket, so it's done by Service Delivery team.

Attachments

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[MarianKijewski]

I've decided to put it in triple ticks so it's easier to copy.

[spoonman01]

What about the "unlock" thing? I think apps are locked by default, does a single Galley request both unlock and enable ?

[MarianKijewski]

Good question. This is what I assumed from swagger docs:
https://staging-nginz-https.zinfra.io/api-internal/swagger-ui/galley/#/galley/iput_AppsConfig

Request body:

{
  "status": "enabled",
  "ttl": "unlimited"
}

Response:
200

{
  "lockStatus": "locked",
  "status": "enabled",
  "ttl": "unlimited"
}

But this is just an example, so it might be wrong.
Best thing would be to actually try it.
I'll ask SD if we can connect to the team they gave us, or just answer the question.

[MarianKijewski]

Confirmed with SD team that the lockStatus is only for the features that are managed in Team management by team admins.
So you can change stuff via backoffice or galley API even if it's locked. By unlocking it you're enabling team admins to toggle it in TM, but that's not even possible since there's no UI for it.

[bbaarriiss]

Maybe instead of multiple "raise a [support ticket]" in different rows, we can mention it once say sth like "You should raise a ticket to have MLS and app feature flag bla bla"

So the customer will create one ticket for all. We better make people's life easy imo.