-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Enhancement Description
Right now, the Console Framework Client can only provide benefit to an Axon Framework application IF the user defined a token in their application.
This makes sense, as for a live connection with past information, we simply require some form of validation.
However, we can still provide benefit to the user, even when there is no token.
We could perform a basic "update check" from the console client to AxonIQ Console.
This update check would hit an endpoint of AxonIQ Console's main backend (called console-web), sharing Axon dependency versions.
Be mindful that we should only do this for Axon dependencies! Exposing versions of other dependencies is not feasible for this use case. Once the console client shares the Axon-version info to Console, Console can reply with "up to date" or "out of date." Especially when CVEs are in play, we should be very clear that an update is recommended.
So, in all, the process would be something like this:
- The
console-framework-clientnotices there is no token to connect with AxonIQ Console, or the token fails to connect. - In absence of the token, it getters the Axon-version info.
- It invokes the "update checker" endpoint with the Axon-version info.
- We wait for the response and log it on arrival.
Lastly, users should be able to disable this default approach if they want to.
Current Behaviour
The console-framework-client only does anything when a workable token is present.
Wanted Behaviour
When console-framework-client is unable to make a connection to AxonIQ Console, that if falls back to the update checker flow described above.
Possible Workarounds
None