-
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
[Ingest] Add additional safeguards for data source wizard step 2 #60426
Conversation
Pinging @elastic/ingest-management (Feature:Fleet) |
@@ -183,7 +183,10 @@ export const StepConfigureDatasource: React.FunctionComponent<{ | |||
// Step B, configure inputs (and their streams) | |||
// Assume packages only export one datasource for now | |||
const ConfigureInputs = | |||
packageInfo.datasources && packageInfo.datasources[0] ? ( | |||
packageInfo.datasources && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about using typescript coalescing here(packageInfo.datasources?.[0]?.inputs?.length ?? false) ? (<>) :
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elasticmachine merge upstream |
💚 Build SucceededTo update your PR or re-run it, just comment with: |
Co-authored-by: Elastic Machine <[email protected]>
I wonder if the user should ever get to this step 2? I think if someone wants to configure the endpoint package, we should send him directly to endpoint UI. |
* master: [ML] Re-enabling file upload telemetry (elastic#60418) [NP] Use local helper shortenDottedString for discover (elastic#60271) [Console] Fix for `_settings` and x-pack autocomplete (elastic#60246) Task/host enhancements (elastic#59671) [Search service] Asynchronous ES search strategy (elastic#53538) Index Action - Moved index params fields to connector config (elastic#60349) Edits UI text for ML nodes and job button (elastic#60184) Publish getIsNavDrawerLocked$ method on core chrome service. (elastic#60191) Disabled edit alert button on management ui for non registered UI alert types (elastic#60439) Revert "[Console] Fix bool filter autocompletions and refactor (elastic#60361)" [Console] Fix bool filter autocompletions and refactor (elastic#60361) Update ingest management team handle (elastic#60457) [IM] Use EuiCodeBlock to render index mapping (elastic#60420) Add additional safeguards for data source wizard step 2 (elastic#60426) [kbn/pm] don't fail when plugins are outside repo (elastic#60164) upgrade react-use (elastic#60427) Remove link to old settings (elastic#60326) Update app arch CODEOWNERS items. (elastic#60396) [ML] Fixing custom urls to dashboards (elastic#60355) Update the ems-client dependency to 7.7.0 (elastic#59936)
@ruflin I was wondering the same thing. Or, only allow the user to add a name + description on the ingest side and show a message that Endpoint datasource can be configured on the endpoint app after being added to the Agent Config. |
) Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Re: Step 2 when using Endpoint - we discussed this during design sync today, final flow TBD but I think we will still keep this overall flow with a message saying that the data source will be created with a recommended Endpoint policy. |
@jen-huang sounds good :) |
Summary
This PR adds additional null checks for step 2 of the data source wizard. Issue surfaced from Endpoint package, which exports no inputs: elastic/package-registry#260 (comment)