Skip to content

Commit 21c2dea

Browse files
committed
Add Keyrings and Import sections to Concepts page.
1 parent 123a77b commit 21c2dea

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

fern/docs/pages/concepts.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,16 @@ For example, if you want to collect webhook events from an organization's GitHub
3737
The framework for executing code provided by users is [functions](/snapin-development/references/functions). Currently, Javascript/TypeScript can be taken as input from the user and deployed as a function.
3838

3939
Connection values can be passed to a function at runtime, enabling it to execute API calls to DevRev and to external systems such as GitHub, Slack, Bitbucket, and Discord.
40-
g
40+
41+
## Keyring
42+
43+
A [keyring](/snapin-development/references/keyrings/introduction) is a collection of authentication information for external systems. This includes the key (e.g., a PAT token or API key), its type, the organization ID for which a key is valid,
44+
and in some cases the organization name. A keyring is used by a snap-ins to authenticate to the external system in API calls.
45+
46+
## Imports
47+
48+
Snap-ins that provide an extractor function for an [ADaaS](/snapin-development/adaas/overview) snap-in responsible for extracting data from an external system need to have an import section defined in their manifest to register their snap-in in the **Imports** section of the DevRev app.
49+
4150
## Globals
4251

4352
Snap-ins can be configured to enable and disable features, based on custom inputs defined by the developer and provided by the installer.

0 commit comments

Comments
 (0)