[Multiple Datasource][Version Decoupling] Add data source version and installed plugins in MDS data source viewer returns

[ZilongX]

Description

• This one is to add fields dataSourceVersion and installedPlugins in all data source viewers.
• These two metadata would be consumed by plugins to perform data source filtering and decoupling check

Issues Resolved

#7099

Screenshot

Changelog

• fix: [MDS][Version Decoupling] Add dataSourceVersion' and 'installedPlugins in viewer returns

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[github-actions]

❌ Entry Too Long

Entry is 106 characters long, which is 6 characters longer than the maximum allowed length of 100 characters. Please revise your entry to be within the maximum length.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.58%. Comparing base (1cb5956) to head (fc6af23).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7172   +/-   ##
=======================================
  Coverage   67.57%   67.58%           
=======================================
  Files        3469     3469           
  Lines       68497    68499    +2     
  Branches    11138    11138           
=======================================
+ Hits        46288    46292    +4     
+ Misses      19503    19502    -1     
+ Partials     2706     2705    -1     

Flag	Coverage Δ
Linux_1	33.15% <ø> (ø)
Linux_2	55.25% <ø> (ø)
Linux_3	45.31% <100.00%> (?)
Linux_4	34.72% <0.00%> (-0.01%)	⬇️
Windows_1	33.20% <ø> (ø)
Windows_2	55.21% <ø> (ø)
Windows_3	45.32% <100.00%> (+<0.01%)	⬆️
Windows_4	34.72% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kavilla]

This is cool. Thank you!

I haven't looked how this is set. Like is this set just one time when the datasource is added or is it anytime the datasource is selected?

Also do we plan on utilizing the capabilities service, for example link. For example, query assist there could be ML commons installed but doesn't have the chat feature.

We could use the capabilities service for OSD plugins on the remote cluster to emit the capabilities that cluster has when it starts up and emit to the caller.

[ZilongX]

This is cool. Thank you!

I haven't looked how this is set. Like is this set just one time when the datasource is added or is it anytime the datasource is selected?

Also do we plan on utilizing the capabilities service, for example link. For example, query assist there could be ML commons installed but doesn't have the chat feature.

We could use the capabilities service for OSD plugins on the remote cluster to emit the capabilities that cluster has when it starts up and emit to the caller.

It's onetime when the data source lists are loaded from saved objects. Basically this one to extend the fetch fields adding two more data source metadata in the returned list.

For leveraging of the capabilities service based on my current knowledge not yet, might be a promising one though and I'll check it out, but more it would be each individual plugin's choice preference.