-
Notifications
You must be signed in to change notification settings - Fork 444
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
Elastic connector integration #10898
Conversation
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 from the Search side. Two small comments.
kibana: | ||
version: "^9.0.0" | ||
elastic: | ||
subscription: "basic" |
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.
CC @danajuratoni - I expect we actually want this platinum+, but since it'll only be accessible through Agentless (cloud and serverless) maybe this doesn't matter?
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.
@seanstory This should be standard (I confirmed with Dana). Looking at integration manifest only 4 options are supported in enum: basic, gold, platinum and enterprise. So I think in such a case: basic == standard?
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.
I expect we actually want this platinum+, but since it'll only be accessible through Agentless (cloud and serverless) maybe this doesn't matter?
This is a great place to get our wires crossed, so I'd like to double check:
- licensing for Elastic managed connectors (i.e. Agentless connectors) should remain unchanged. This means Standard on Elastic Cloud hosted.
- licensing for connectors on Agent (i.e. self-managed connectors via Agent) is not part of 9.0, but should be equivalent to self-managed connector clients. This would mean likely Platinum+ for self-managed connectors via Agent, final decision to be made in the future / if and when we'll add support.
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 approach we took makes it hard if not impossible for users to run this on agent so I wouldn't worry about the self-managed agent case. But I'm following up on this thread.
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.
"standard" == "platinum" IIRC. Standard is our lowest tier in cloud, but it's still a paid tier, to it's higher than basic.
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.
🤯 Good point, Sean. We need to verify that the cloud standard
license is included if we enforce platinum
in the integration definition.
…l previews, please remove prerelease tag
Setting the Kibana version restriction to 9+ is causing a Buildkite error. I’m thinking we need to point it to an existing version instead
|
enabled: false | ||
agentless: | ||
enabled: true | ||
multiple: 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.
pay attention a user will be able to enable more than one input using the high-level tile.
Correct me if I'm wrong @jsoriano but there's no way to validate there's only one input in use, correct?
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.
Is there actually a way for us to hide/disable this high-level tile? Since we really only want one input at a time, only the lower-level tiles really make sense for us.
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.
not that I know of
with CSPM integration the top-level tier doesn't serve our use case either. When we thought of enabling such capability we noticed that in the fleet, the top-level tier is used in multiple flows, so it seemed like a big change at the time to address. We ended up having a custom UI component instead.
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.
We ended up having a custom UI component instead.
Can you elaborate?
template_path: github.yml.hbs | ||
- name: google_drive | ||
title: Google Drive Connector | ||
icons: |
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.
nit: going forward it is recommended to have screenshots per policy_template
deployment_modes: | ||
default: | ||
enabled: false | ||
agentless: |
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.
FYI we'll soon require some owner tags as part of this section.
It's not yet part of the spec but you can follow here to add it when it'll be added to the spec:
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.
I assume this won't block us from merging, will just be something we need to add to a todo list?
buildkite test this |
💚 Build Succeeded
History
|
Quality Gate failedFailed conditions |
Can I ignore this? Looks like the PR would let me merge as is, but I don't want to skip something I shouldn't |
Forgiveness over permission 🤞 |
Package elastic_connectors - 0.0.1 containing this change is available at https://epr.elastic.co/search?package=elastic_connectors |
Proposed commit message
Initial implementation of the package for the connectors service, running exclusively in agentless mode. The package supports ~ 30 connector types (e.g., Google Drive, SharePoint, MongoDB), each syncing data to an ES index. We have a
policy_template
per connector type, so that we have a unique tiles displayed the integrations UI. This PR just adds support for Google Drive and Github Connectors.Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots