Skip to content
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

[Ingest Manager] Designs for enabling experimental packages #69740

Closed
hbharding opened this issue Jun 23, 2020 · 9 comments
Closed

[Ingest Manager] Designs for enabling experimental packages #69740

hbharding opened this issue Jun 23, 2020 · 9 comments
Assignees
Labels
design Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@hbharding
Copy link
Contributor

Per #64869, we need a way to enable the use of experimental packages. This will be useful for development purposes, but users may be interested in trying these out too. Currently, we display experimental packages by default, which makes the registry look a bit messy.

In addition to being able to toggle their display, we should indicate whether a package is GA, Beta, or Experimental.

@hbharding hbharding added design Team:Fleet Team label for Observability Data Collection Fleet team labels Jun 23, 2020
@hbharding hbharding self-assigned this Jun 23, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@hbharding
Copy link
Contributor Author

hbharding commented Jun 24, 2020

Update:

Screencast explanation

We can add a switch toggle on the integrations page to hide/show experimental integrations. This will be turned off by default. If an integration is experimental, we use a badge on the card at the top. We can also use this badge on the integration detail page in the header.

image
image

cc @ruflin @jen-huang @mostlyjason @ph

@hbharding
Copy link
Contributor Author

I updated the screenshots to show 2 additional things:

  • Integrations can also be Beta. If so, use a beta badge on the integration card and in the integration detail page header.
  • I added a tooltip to the experimental toggle and the badge

@jen-huang
Copy link
Contributor

jen-huang commented Jun 25, 2020

@hbharding Are Beta integrations affected by the Experimental toggle?

Got clarification that the experimental toggle only affects visibility of experimental integrations, not beta ones. We always show beta integrations.

@hbharding
Copy link
Contributor Author

Sorry yup, should have included that :)

@hbharding
Copy link
Contributor Author

Update:

During our weekly team sync, we learned that the majority of our integrations will be experimental for our next release. We discussed that we can probably hold off on implementing this until more of our integrations are beta.

@epixa
Copy link
Contributor

epixa commented Jul 8, 2020

@hbharding Can you clarify the reasoning behind that decision? We need people to use the experimental packages in order for them to advance to beta, so this feature is still important for experimental packages in my mind.

@jen-huang
Copy link
Contributor

jen-huang commented Jul 8, 2020

@epixa Hi Court, the part about "hold off on implementing this" really just refers to holding off implementing a toggle to show experimental packages. For beta, we will show all experimental packages by default because most packages will be experimental in this release. PR with implementation screenshots: #70997

In a later release when more packages move out of experimental, then we will add a toggle or setting to enable showing experimental packages.

@jen-huang
Copy link
Contributor

Closing as #70997 is merged.

@hbharding I tagged #64869 with the design label to reassess what kind of toggle to implement for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

6 participants