-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Have an experimental config option for packages #64869
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@ph I think it is pretty imporatnt that we get this in for packages. |
As part of #70026, we decided to show all experimental packages by default for beta release so no toggle or option is needed. I'm removing the priority on this and moving this back to our Inbox to be triaged for the next release. |
moved it to 7.10 |
Move that to This look more like a product decision related to discovery, @mostlyjason Not a priority right now but something to track for the integration UI. |
Putting this in backlog to revisit once more packages move out of Experimental. |
Packages in the package manager have 3 release types: ga, beta, experimental. The same is the case for the datasets inside each package. See elastic/package-registry#382 for more details.
By default the
/search
endpoint in the registry only returns ga and beta packages. To also view experimental packages, the flag/search?experimental=true
has to be passed in.Currently we show all experimental packages by default. We should have a setting in the Ingest Manager UI to enable experimental packages and datasets. These would then also be shown in the package overview and when creating a data source.
At the moment we show experimental datasets also in the UI by default. We should hide these and only show if experimental config is set to true.
It would be also possible to have 2 different configs: 1 for packages and one for datasets.
The text was updated successfully, but these errors were encountered: