It would be great to be able to create, delete, list, enable and disable heartbeats to make it easier to maintain a number of endpoints via CLI.
For context, we maintain ~250 heartbeats, one for each cluster we manage, and while we have automated creation/deletion via a Kubernetes operator, sometimes a need comes up to check them and enable/disable for maintenance.
There is currently a heartbeat command, but it can only send pings to already existing and enabled heartbeat endpoints. It would probably make sense to re-factor it and move functionality into a subcommand like heartbeat ping in order to be able to add others, e.g. heartbeat create, heartbeat delete, etc. Or, what your preference for the UI be?
It would be great to be able to create, delete, list, enable and disable heartbeats to make it easier to maintain a number of endpoints via CLI.
For context, we maintain ~250 heartbeats, one for each cluster we manage, and while we have automated creation/deletion via a Kubernetes operator, sometimes a need comes up to check them and enable/disable for maintenance.
There is currently a
heartbeat
command, but it can only send pings to already existing and enabled heartbeat endpoints. It would probably make sense to re-factor it and move functionality into a subcommand likeheartbeat ping
in order to be able to add others, e.g.heartbeat create
,heartbeat delete
, etc. Or, what your preference for the UI be?