When "enable_new_services=False" specify a disable reason
Add a new configuration option "new_services_
as disable reason when a new service is added and "enable_
By default the disable message would be simply: "New service"
Services can be disabled by several reasons and the admins can use the API to
specify a reason. However, currently if new services are added and
"enable_
Having services disabled with no reason specified creates additional checks
on the operators side that increases with the deployment size.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Belmiro Moreira
- Direction:
- Needs approval
- Assignee:
- Belmiro Moreira
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Belmiro Moreira
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add disable reason when enable_
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
