Individual Application updates #1228
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#289 key features improving user experience supported
fediversity/fediversity
#159 Hosting providers can update their operators' deployments
fediversity/fediversity
Reference
fediversity/fediversity#1228
Loading…
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 Hosting Provider,
I want to roll out Application updates without delay,
so that my Operator customers can enjoy the latest features and security
fixes.
notes
Being able to deploy gradually across Operators would go a step further and
prevent a broken update from affecting all Operators that deploy the
Application.
maybe our existing
PIN_EFFECTmechanism could be extended to zoom into arbitrary parts of a module to this endwithin the context of a given deployment, i guess the info to keep everything else a no-op should be there.