Delete a knowledge source including all associated resources such as sync settings, datastores, and bucket files.
Bearer token authentication. Format: 'Bearer
Successful Response
Represents managed knowledge sources. These are managed by a system admin or Genow. Each managed knowledge source has a corresponding permission that looks like this: useCase.<use_case_id>.knowledgeAsset.<knowledge_asset_id>.knowledgeSource.<source_id>.read Permissions on knowledge sources are granted in the context of the use case and knowledge asset that the source is assigned to.
Example: Let's say there is a managed knowledge Asset with the id 'asset-1' that contains two managed knowledge sources with the ids 'source-1' and 'source-2'. asset-1 ├── source-1 └── source-2 If a user has the permission 'useCase.use-case-1.knowledgeAsset.asset-1.knowledgeSource.source-1.read', they can see 'asset-1' in the frontend, and if they search on that asset, they will only be able to access sources from source-1 and documents from source-2 will not be included in the search. Wildcards can be used in permissions to grant access to all knowledge sources in a use case or knowledge asset. For example, if a user has the permission 'useCase.use-case-1.knowledgeAsset.asset-1.knowledgeSource.*.read', they can see 'asset-1' in the frontend, and if they search on that asset, they will be able to access all sources from 'asset-1'.
Represents the type of file sources that are within the knowledge source.
agent-builder, cloud-bucket, external-web-search, disa-agent, one-losp-agent-lmh, one-losp-agent-still, one-losp-agent-still-specialized-teams, sap-btp-agent, direct-url Enumeration for the different permissions types associated with knowledge sources
personal, managed x <= 100