Considering the use cases you have mentioned ,the service entries are really important in db and we should not delete it at startup, rather we should provide an API 'service-remove' as John suggested to remove the particular service on user-request.
I don't think we should completely leave it to the user's consent to delete a service without proper sanity checks.
Rather we should discuss similar use-cases(like if a volume/snapshot with the given host name is present) where the user should not be allowed to delete the service entry. Based on those use-cases we should filter request and proceed with delete.
Hi Rajini and John :
Considering the use cases you have mentioned ,the service entries are really important in db and we should not delete it at startup, rather we should provide an API 'service-remove' as John suggested to remove the particular service on user-request.
I don't think we should completely leave it to the user's consent to delete a service without proper sanity checks.
Rather we should discuss similar use-cases(like if a volume/snapshot with the given host name is present) where the user should not be allowed to delete the service entry. Based on those use-cases we should filter request and proceed with delete.