Conversation
🔍 Preview links for changed docs |
src/platform/packages/shared/kbn-connector-specs/src/specs/brave_search/brave_search.ts
Show resolved
Hide resolved
| .describe('Result offset for pagination'), | ||
| }), | ||
| output: z.object({ | ||
| query: z.any().describe('Original query information'), |
There was a problem hiding this comment.
The remote API does have a strict definition:
https://api-dashboard.search.brave.com/app/documentation/web-search/responses
Do we want to be loose to avoid breaking on any changes from that API and only fixing any downstream users of this response?
There was a problem hiding this comment.
That's my instinct, yeah. At least for now. Maybe we'll want to tighten this if/when we build an OOTB workflow that needs to depend on specific fields.
0b41c8c to
33fffa5
Compare
33fffa5 to
8213616
Compare
Add docs, tests, and internationalization Add brave search docs to the TOC Add brave search do stack connectors snippet Fix the syntax issue
fdff411 to
00711ac
Compare
| @@ -2314,6 +2314,7 @@ src/platform/packages/shared/kbn-connector-specs/src/all_specs.ts | |||
| src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts | |||
There was a problem hiding this comment.
@seanstory could you please add this line? thanks!
| src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts | |
| src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts | |
| src/platform/packages/shared/kbn-connector-specs/src/specs/** @elastic/workflows-eng |
There was a problem hiding this comment.
no - we don't want every new spec to require the review of the workflows-eng folks. If my team (E&T) adds a new connector (like this Brave Search connector) I shouldn't need the Workflow team's approval. Ideally, I wouldn't need anyone's approval but my own team.
There was a problem hiding this comment.
Then we should keep it empty, otherwise it requires a review from the Response Ops team, like in this PR.
FYI, CODEOWNERS rules are applied from the main branch, not from the PR branch.
src/platform/packages/shared/kbn-connector-specs/src/specs/**
There was a problem hiding this comment.
src/platform/packages/shared/kbn-connector-specs/src/specs/**
src/platform/packages/shared/kbn-connector-specs/src/all_specs.ts
src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts
src/platform/packages/shared/kbn-connector-specs/src/specs/alienvault_otx/** @elastic/workflows-eng
src/platform/packages/shared/kbn-connector-specs/src/specs/brave_search/** @elastic/workchat-eng
vs
src/platform/packages/shared/kbn-connector-specs/src/all_specs.ts
src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts
src/platform/packages/shared/kbn-connector-specs/src/specs/alienvault_otx/** @elastic/workflows-eng
src/platform/packages/shared/kbn-connector-specs/src/specs/brave_search/** @elastic/workchat-eng
vs
src/platform/packages/shared/kbn-connector-specs/src/specs/alienvault_otx/** @elastic/workflows-eng
src/platform/packages/shared/kbn-connector-specs/src/specs/brave_search/** @elastic/workchat-eng
Are all functionally equivalent, AFAICT? And yes, right now they all end up requiring a review from response ops when new connectors are added, because all_specs.ts and connector_icons_map.ts always get changed. There's not a good single-team owner for these, I don't think. The only solution IMO is to adjust these files to automatically detect specs/icons based on the folders available, rather than on new code lines that must be added. OR, response-ops has to always approve new connectors, and at least doesn't get bothered when existing connectors are modified.
WDYT?
There was a problem hiding this comment.
I'm know sure if they are equivalent, because rules listed below overrides the top rules.
src/platform/packages/shared/kbn-connector-specs @elastic/response-ops <- set a default owner
src/platform/packages/shared/kbn-connector-specs/src/all_specs.ts <- removes any team as owner (it works!)
src/platform/packages/shared/kbn-connector-specs/src/connector_icons_map.ts <- removes any team as owner (it works!)
src/platform/packages/shared/kbn-connector-specs/src/specs/** <- should also remove any team as owner
src/platform/packages/shared/kbn-connector-specs/src/specs/alienvault_otx/** @elastic/workflows-eng <- set ownership per folder spec
florent-leborgne
left a comment
There was a problem hiding this comment.
LGTM from a docs perspective. Thanks for updating this with the structure we discussed in the other PR 🚢
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
History
|
Summary
Adds a connector for Brave Search to the new "v2" framework.
This is an API we've found useful for doing web search in workflows and with Agent Builder.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelinesRelease Notes
Introduces a connector for web search via Brave Search