Closed smith closed 1 month ago
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)
@smith are we sure we want to enable this with the observability:entityCentricExperience
advanced setting instead of using the xpack.inventory.enabled
flag in thekibana.yml
before all the development is finished?
This issue was in the "Ready" column, and I started working on it, but this question came to mind.
cc:@roshan-elastic, @cauemarcondes, @kpatticha
@smith are we sure we want to enable this with the observability:entityCentricExperience advanced setting instead of using the xpack.inventory.enabled flag in thekibana.yml before all the development is finished?
Yes. The difference between the two is:
If the advanced setting is enabled and a user sees technical preview software on serverless that is not finished it is not a problem.
The next release feature freeze is October 15 and at that time things will be in a much less unfinished state.
If the advanced setting is enabled and a user sees technical preview software on serverless that is not finished it is not a problem.
This is the answer I was looking for, thanks @smith!!
@iblancof feel free to raise any questions or concerns, even if the ticket is in the "Ready" state.
In https://github.com/elastic/kibana/pull/191798 the visibility of the inventory navigation is controlled by the kibana.yml setting
xpack.inventory.enabled
. It should use theobservability:entityCentricExperience
advanced setting instead.✔ Acceptance critieria
xpack.inventory.enabled
does not exist (it can be removed without deprecation since it was never used by customers)observability:entityCentricExperience
advanced setting is enabled I can see and use the top-level inventory navigation.