feat(#4253): render html content that is returned in info / health endpoint

[SteKoe]

[cdprete]

Nice @SteKoe.

Is the JSON returned by an info indicator scanned fully for it or are there some sort of depth or structure limits?
For example:

• links are searched only up to 2 nested levels
• links are only searched in objects and not arrays

Also, the links are updated any time the info are fetched, right?
I'm asking this to avoid potential caching issues that may show the old links when the info changed.

In my use case, I've an info contributor that renders a link to a daily and monthly file.
Of course, the daily file changes every day while the monthly one only once a month when it gets generated.

[SteKoe]

Hi!

some sort of depth or structure limits?
No limits.

Also, the links are updated any time the info are fetched, right?
SBA does not cache on its own. So whenever the info changes, the links should update, too.

[cdprete]

Hi!

some sort of depth or structure limits?
No limits.

Also, the links are updated any time the info are fetched, right?
SBA does not cache on its own. So whenever the info changes, the links should update, too.

Thanks for confirming these.

[cdprete]

Hello @SteKoe.
I updated my DEV and QA environments to 3.5.6, but it seems like the autolink feature is not working, at least for the health indicators. For example:

is rendered as plain text, but now the service-url overwrite that comes from the metadata gets rendered as a link automatically:

So, I wonder how the feature should then really work...

[cdprete]

Hi @SteKoe.
For some reason, it seems to not be working in the health part. See below:

The <a> tag gets rendered as it is instead of being rendered as a link.