Runtime: APIs to get connector details for a project #4363
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds three new APIs:
ListConnectorDrivers
: returns metadata about all connector drivers implemented in the runtime, including specs of the config properties they support. It replaces the previousListConnectors
API.AnalyzeConnectors
: parses the project files and returns a complete breakdown of all connectors declared or referenced in the project, as well as the values of their config properties (broken down by source, e.g.rill.yaml
or.env
).ListNotifierConnectors
: is an API for getting the connectors that can be used as notifiers. It's designed specifically for use in the cloud UI to determine which alert/report destinations are available. Unlike AnalyzeConnectors, it does not require admin-level permissions (and is much faster). Note: It will not work correctly until this PR merges: Slack integration for alerts and reports #4371.Closes https://github.com/rilldata/rill-private-issues/issues/216