feat: extract option-rename mappings to migrate stored form configs #1073
No reviewers
fediversity/developers
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
fediversity/fediversity!1073
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:schema-changes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #629.
Auto-migrates configurations in the api and browser according to alias/rename metadata extracted from the new nix module.
Further unproxies api's schema-get end-point invocation in the panel test to not go thru the panel.
a853e9e2940a6c264ac7a7fc1f1ee6e1f7d5b8e5f4fbd3cd951cd27bdc7956d520ccf5a1d764ddffWIP: feat: extract option-rename mappings to migrate stored form configsto feat: extract option-rename mappings to migrate stored form configs82f598b24ec22acbeb99