-
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
[Connectors] Checking for undefined config and secrets during connector validation #122696
Conversation
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.
Changes LGTM!
Tested with an email connector w/ username - password that was created in 7.15. I was able to see the difference after upgrading to main vs this PR and the error message change 👍
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @ymao1 |
…or validation (elastic#122696) * Checking for undefined config and secrets during connector validation * Adding functional tests Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit d19a2f3)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…or validation (#122696) (#123369) * Checking for undefined config and secrets during connector validation * Adding functional tests Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit d19a2f3) Co-authored-by: ymao1 <[email protected]>
Resolves #122346
Summary
With this PR, we added validation of connector config and secrets together. This validation was only added to the email connector. We've found that in cases where the connector
secrets
field is undefined, this will lead to a null accessor error (Cannot read properties of undefined
) when executing connector action (either via the test connector UI or during actual action execution. Thesecrets
value can become undefined due to decryption errors during migration.To Verify
secrets must be defined
instead ofCannot read properties of undefined
Checklist