user control over update timing #206
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
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.
Depends on
#304 reference front-end is decoupled from version of configuration module
fediversity/fediversity
Reference: fediversity/fediversity#206
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
As a user, I want to retain control over when to deploy state/application updates, so that I can plan downtime at a time that is more convenient.
today we had a meeting on this, tho scoped down to consider updating all applications for a user at once, rather than individually.
this seemed to already imply having to switch state representations to json (validated by json schema) to decouple our django application from the versions to be deployed.
as per @koen we may currently regard this use-case out-of-scope.
nevertheless, the architectural concerns w.r.t. decoupling may nevertheless remain relevant for the purpose of migration (#100).
kiara referenced this issue2025-02-26 11:23:55 +01:00