Require UUIDv7 for serviceowner-provided ids

[oskogstad]

Introduction

This change introduces a UUIDv7 requirement for dialogIds, transmissionIds and activityIds

Description

To avoid fragmentation issues caused by the inherit randomness of UUIDv4 values in b-tree indexes, we will require all self-supplied IDs to be UUIDv7, which are stored sequentially and lets eg. joins be perfomed better.

Implementation

A valication routine will have to at a minimum check that the correct version bits are set. We need to consider if the timestamp part (the first 48 bits) should be validated somehow. Only accepting values within a small window relative to server time will not work, as items might be been generated on the server provider side much earlier. A more lax validation (eg. must be after 2010 and not in future) might be more suitable.

Tasks

Preview Give feedback

1. Implement validation checks for dialogIds, transmissionIds and activityIds
2. Update documentation
3. Add unit test

Threat modelling

Preview Give feedback

1. Does this change introduce any potential security issues?

[elsand]

Refinement: There are serious concerns about index fragmentation and performance issues stemming from spamming the b-tree index with UUIDv4 values from Altinn 3/2 instances. This will probably negatively affect the index performance, even if we at a later stage introduce v7 requirements.

We work to have Altinn 3 apps start using UUIDv7 as their PKs. In order to support historic instances, they will need to introduce as "dialogId" column containing the UUIDv7 value. This should be pre-generated and stored before transferring in order to ensure idempotence and avoid duplications.

This change is to be considered breaking, and will have to be communicated with service providers.