Disable a system without sabotaging the config

Not planned

Follow

Ole Dale

• November 18, 2020 14:19
• Edited

It would be nice to be able to have an option disable a system without breaking the configuration. Currently the options are pull and restart, but no start/stop option. 

The background for this request was the need to disable a misbehaving microservice and the only methods would be removing the system or breaking the configuration on purpose. 

4

• Official comment

  

  Geir Ove Grønmo

  • December 15, 2020 10:15

  This is a good idea and we have a task for this in our backlog, but we'll not prioritize this at this time. If you have more practical examples/use-cases for when this would be a useful feature that'd be helpful.

  Comment actions Permalink
• 

  timur.samkharadze

  • November 23, 2020 14:22

  This one would be very nice to have!

  0

  Comment actions Permalink
• 

  timur.samkharadze

  • December 15, 2020 13:02

  Geir Ove Grønmo it would be especially useful for dev/test nodes which rely on embedded data and usually quite small sized. It would free some resources which each unused but running service consume.

  0

  Comment actions Permalink
• 

  Geir Ove Grønmo

  • December 15, 2020 13:33

  Indeed. That's a very good point. That could also be implemented via a property on the microservice system that basically told if the microservice should be provisioned or not. Environment variables could then be used to control this. A general system disable/enable feature would also be nice of course.

  0

  Comment actions Permalink

Please sign in to leave a comment.