Exit 1 on hot startup failure

[brtkwr]

Describe the bug

If TOKENS is provided and the bootstrap fails, it appears as though unleash-edge starts anyway. Is it possible to force application to exit so that unleash-edge can retry bootstrapping? We don't want a new unleash-edge deployment to replace the existing if the bootstrapping has failed for whatever reason.

Steps to reproduce the bug

No response

Expected behavior

No response

Logs, error output, etc.

No response

Screenshots

No response

Additional context

No response

Unleash version

No response

Subscription type

None

Hosting type

None

SDK information (language and version)

No response

[sjaanus]

Hey @brtknr , thank you for contacting us. What tokens are you providing? Are they valid? Do you know why the bootstrap process is failing?

[brtkwr]

Hi @sjaanus, my thinking around this is if the unleash instance is unavailable and unleash-edge is not able to contact the main unleash server to bootstrap the flags, I don't want my existing deployment to be replace until the new deployment is hot bootstrapped. Does that make sense?

[sjaanus]

Sure, in this situation, you should use the edge readiness check. You can find more information about it here: https://docs.getunleash.io/reference/unleash-edge#built-in-ready-check. The edge will become ready as soon as it receives the feature flags. 😊