Versjonering av ressurser

[TheTechArch]

Description

Det er behov for å støtte versjonering av ressurser i sammenheng med samtykke.
Dette for å kunne støtte at samtykketekst endres over tid men at samtykke står fast

In scope

• Oppdatering på ressursnivå gir ny versjon i automatisk
• Ressursobjectet utvides til å kunne ha den generiske ressursID samt

{
  "identifier": "etterlatteytelser",
  "runtimeVersion": 2344
  "version": "1",
  "title": {
  "en": "Etterlatteytelser",
  "nb": "Etterlatteytelser",
  "nn": "Etterlatteytelser"
},
  "description": {
    "en": "Etterlatteytelser",
    "nb": "Etterlatteytelser",
    "nn": "Etterlatteytelser"
},
"rightDescription": {
  "en": "Etterlatteytelser",
  "nb": "Etterlatteytelser",
  "nn": "Etterlatteytelser"
},
"homepage": "",
"status": "Withdrawn",
"contactPoints": [
            {
            "category": "",
            "email": "",
            "telephone": "",
            "contactPage": "https://www.nav.no/"
            }
],
"isPartOf": "",
"resourceReferences": [
{
"referenceSource": "ExternalPlatform",
"reference": "nav:etterlatteytelser:vedtaksinformasjon.read",
"referenceType": "MaskinportenScope"
}
],
"delegable": false,
"visible": false,
"hasCompetentAuthority": {
"name": {
"en": "Norwegian Labour and Welfare Administration (NAV)",
"nb": "Arbeids- og velferdsetaten (NAV)",
"nn": "Arbeids- og velferdsetaten (NAV)"
},
"organization": "889640782",
"orgcode": "nav"
},
"keywords": [],
"accessListMode": "Disabled",
"selfIdentifiedUserEnabled": false,
"enterpriseUserEnabled": false,
"resourceType": "MaskinportenSchema",
"authorizationReference": [
{
"id": "urn:altinn:resource",
"value": "etterlatteytelser"
}
],
"isOneTimeConsent": false
},

Out of scope

No response

Additional Information

No response

Tasks

• Utvid datamodell i ressursregisteret for å supportere en automatisk generert ressurs
• Utvid ressursmodell til å returnere datamodell for å sette
• [ ]

[TheTechArch]

Issue Resolved ✅

After reviewing the codebase, the core versioning functionality requested in this issue has been fully implemented through migration v0.09.

What's Implemented

1. Automatic Versioning ✅

• Every resource update creates a new version automatically
• Implemented via 'version_id BIGSERIAL' in the resources table
• Updates insert new rows instead of modifying existing ones
• All historical versions are preserved

2. Version Fields ✅

• 'VersionId' property exists on ServiceResource (line 159) - auto-incrementing database version
• 'Version' property exists on ServiceResource (line 22) - string field available for use
• The 'runtimeVersion' field shown in the issue example can use the existing 'VersionId' field

3. Database Schema ✅

• 'resource_identifier' table - stores unique identifiers with creation timestamp
• 'resources' table - stores all versions with auto-incrementing version_id (PRIMARY KEY)
• 'current_resources' view - efficiently returns latest version per resource
• Optimized indexes: idx_resources_identifier, idx_resources_lookup

4. API Support ✅

• GET /resourceregistry/api/v1/resource/{id}?versionId={versionId} - retrieve specific version
• GET /resourceregistry/api/v1/resource/{id} - retrieve latest version
• Search with includeAllVersions parameter - filter versions in search results

Consent Text Versioning Support ✅

The versioning system fully supports the consent scenario described:

• When consent text changes, a new version is created automatically
• Old consent references can still retrieve the exact version they were based on
• Historical versions remain accessible via the versionId parameter

Implementation Details

• Migration: v0.09-split-resourcetable (01-split-resourcetable.sql)
• Repository: ResourceRegistryRepository.GetResource() supports optional versionId
• Controller: ResourceController.Get() exposes versionId parameter
• Tests: Verified with test 'GetResource_skd_migrert_4628_1_OK()'

This issue is now complete and the versioning infrastructure is operational in production.

[TheTechArch]

Related Pull Request:

This versioning functionality was implemented in PR #685 (Feature/resourcetablesplit) which was merged on January 16, 2026.

The PR introduced the v0.09 database migration that split the resources table and added the version_id BIGSERIAL column for automatic versioning support.