Update service when hardcoded parameters change #373
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal#373
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?
Stories
As a service operator, I want to make sure service instances adhere to hardcoded parameters when they change
Implementation Notes
As a follow-up to #294: when hardcoded parameters are changed, update all service instances on the control-planes to make sure the new parameters are adapted accordingly.
One example use case: For Codey we hardcode
spec.parameters.service.majorVersion. Once a new Forgejo major version is out, we want to change the version number and make sure all Codey instances are upgraded accordingly.