NET-655

[uGiFarukh]

Describe your changes

• When MQ connection is broken, a fallback thread is being ran every 30s for calling netclient http config pull.
• If peer updates are not received or lost, the same fallback thread will run every 30s for calling netclient http config pull.

Related to -> gravitl/netmaker#2670

Provide Issue ticket number if applicable/not in title

Provide link to Netmaker PR if required

Provide testing steps

Checklist before requesting a review

• My changes affect only 10 files or less.
• I have performed a self-review of my code and tested it.
• If it is a new feature, I have added thorough tests, my code is <= 1450 lines.
• If it is a bugfix, my code is <= 200 lines.
• My functions are <= 80 lines.
• I have had my code reviewed by a peer.
• My unit tests pass locally.
• Netclient & Netmaker are awesome.

[mattkasun]

would it not be simpler to start the fallback go routine in the mq connection lost handler and stop it in the mq connection handler

[mattkasun]

I think this is way over complicated with starting stopping the fallback function all over the place:

just need to start fallback go routine and let it run

func MQFallback(ctx contex.Context, wg *sync.WaitGroup) {
	defer wg.Done()
	for {
		select {
		case <-ctx.Done():
			fallbackTicker.Stop()
			return
		case <-fallbackTicker.C:
			if Mqclient == nil || !Mqclient.IsConnected() {
				response, err := pull(false)
				if err != nil {
					slog.Error("pull failed", "error", err)
				} else {
					MQFallbackPull(response)
				}
			}
		}
	}
}