-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Don't load connectors and connector types when there isn't an encryptionKey #133335
Don't load connectors and connector types when there isn't an encryptionKey #133335
Conversation
Wait for health check result before making requests to connectors and connector types.
@@ -108,12 +108,7 @@ export function AlertsPopover({ | |||
name: 'Alerting', | |||
items: [ | |||
{ | |||
name: ( | |||
<> | |||
{SearchThresholdAlertFlyout} |
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.
This Flyout is already added on line 137.
Removing this to avoid multiple renders and redundant http requests.
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.
thx for fixing this! 👍
Pinging @elastic/response-ops (Team:ResponseOps) |
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.
The code LGTM.
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.
LGTM! Verified that when running without encryption key, the flyout doesn't try to load connector types and doesn't show discard modal on close. Verified that no more duplicate API calls are made. Verified that can create search threshold rule as expected when encryption key is set. Nice job!
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.
Tested locally and LGTM!
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.
LGTM, code review of DataDiscovery.team owned code, thx for the fix!
Wait for health check result before making requests to connectors and connector types.
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
dear @ersin-erdal, can you backport ? many thx |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Wait for health check result before making requests to connectors and connector types. (cherry picked from commit fc76e0c)
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
fixes:#131986
Http requests to connectors and connector-types endpoints return error when there isn't a permanent encryptionKey.
This PR intends to stop making those redundant http requests triggered by RuleAdd flyout.
I also found out that RuleAdd flyout was added to the Discover page twice. This PR removes one of them too.