Open tsullivan opened 1 week ago
Pinging @elastic/appex-sharedux (Team:SharedUX)
Yes and no? Many of our reporting customers are also onprem customers or stateful cloud customers who are still very much "version centric" for compatibility and long term stability interests. Would we be taking away something that they depend on if we remove this?
@petrklapka I would keep this info on the report job document, but in the UI create a conditional to hide this info for serverless deployments. We shouldn't use isServerless
as a flag, but we can come up with something more specific, such as:
if (shouldShowVersion) {
return (
<>Version: ...</>
);
}
We definitely should not be leaking version information in serverless. Why not base it on the isServerless flag? ++ to keeping this for stateful customers
In serverless projects, the Kibana version is a hidden abstraction from the end user. Therefore, when report jobs are displayed we should not show the "Kibana version" line of text in the report job info.
This piece of information is only useful in stateful deployments, when it's possible that users could be calling the public API using job parameters from an older version of Kibana.