You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Github connector only supports syncing documents with .markdown, .md, and .rst file extensions as per the docs. I've been working to add support for exposing Search Connector indices as Knowledge Base content to the Security Assistant within Kibana and was hoping to make the Kibana Documentation available for reference, however since we've moved to using the mdx format for our docs it is not possible to ingest and embed these documents using the Github connector.
Proposed Solution
Add support for syncing and parsing mdx files. In conversations, it seems there might be compatibility issues at the Apache Tika layer, so might be more involved than just adding the file extension on within the Github connector.
Alternatives
Right now the workaround is to make a new branch on the repo and do a bulk rename mdx->md, which is not ideal for widespread adoption.
The text was updated successfully, but these errors were encountered:
Problem Description
Currently the Github connector only supports syncing documents with
.markdown
,.md
, and.rst
file extensions as per the docs. I've been working to add support for exposing Search Connector indices as Knowledge Base content to the Security Assistant within Kibana and was hoping to make the Kibana Documentation available for reference, however since we've moved to using themdx
format for our docs it is not possible to ingest and embed these documents using the Github connector.Proposed Solution
Add support for syncing and parsing
mdx
files. In conversations, it seems there might be compatibility issues at the Apache Tika layer, so might be more involved than just adding the file extension on within the Github connector.Alternatives
Right now the workaround is to make a new branch on the repo and do a bulk rename
mdx
->md
, which is not ideal for widespread adoption.The text was updated successfully, but these errors were encountered: