(Soft) stalled by T419208: 🦄 Modify the existing create wiki endpoint in Platform API - doing it earlier would probably work, but then we're sending data to laravel that it isn't expecting.

Stalled until T419210: 🦄 Create `KnowledgeEquityCreateWikiWizardStep` Card in Platform UI is deployed.

Thanks @Harej, will get this going for you.

@Harej Note that if you don't have a gpg key, we could also use age which is an easier tool to use, it feels much more like ssh keys than gpg. I've assigned it to you so it doesn't get lost in "unassigned" tickets. Feel free to unassign it when you have given us a public key to encrypt the dump with, and we will see that update and prioritise the work for you.

We should create two estimates here, one for "cloud generic swagger" and one for "per instance swagger" to allow Anton to choose the effort vs user impact.

Moved back due to creating the inactive column.

I personally have tried a LOT of the s3-compatible solutions and none of them are simple or solid in my experience. Ones not mentioned in the description:

• SeaweedFS https://github.com/seaweedfs/seaweedfs
• rclone serve s3 https://rclone.org/commands/rclone_serve_s3/
• ceph has s3 built in https://docs.ceph.com/en/latest/radosgw/s3/ and there's a nifty docker setup https://github.com/hetznercloud/ceph-s3-box

Given that google as a data processor is less access to the data than data controller, this is less urgent than it might appear. Informing our users that google has more access to their data is essential and immediate, but that they don't have access is less important. We should still strive to be accurate, but controller is a superset of processor, so we don't have as much urgency. It might help people be slightly happier with the DPA who want to sign up, so that pushes it higher than "we don't need to do this." though.