-
Notifications
You must be signed in to change notification settings - Fork 193
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
draft framework for document handling #4774
Conversation
👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
|
||
![example payload inbound webhook connector](./assets/inbound-webhook-document.png) | ||
|
||
### Outbound (REST and IDP-related) Connectors |
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.
@crobbins215 Can you clarify for me which Connectors this will apply to so I can apply the appropriate content to those docs?
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.
@christinaausley The wording "IDP-related" is too generic and might not be clear to readers.
I'm aware that the following connectors can support files: inbound Webhook connector, outbound REST and Email connectors.
@chillleader Any other connectors that we should mention here?
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.
Here's the latest list of connectors supporting document capabilities:
- Webhook
- REST
- AWS Textract
- AWS Bedrock
- AWS S3
- BOX Connector
- IDP (extraction) connector - but it's for internal use as far as I know
Another one upcoming - Google Drive.
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.
Two small, non-blocking comments so far, but otherwise this looks good to me!
@christinaausley what's the status of this PR? Are you planning for it to go out tomorrow with alpha3? |
@akeller I have connected with @volodymyr-melnykc via Slack for one final approval before merging 😄 |
|
||
![example payload inbound webhook connector](./assets/inbound-webhook-document.png) | ||
|
||
### Outbound (REST and IDP-related) Connectors |
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.
@christinaausley The wording "IDP-related" is too generic and might not be clear to readers.
I'm aware that the following connectors can support files: inbound Webhook connector, outbound REST and Email connectors.
@chillleader Any other connectors that we should mention here?
@chillleader @volodymyr-melnykc This is ready for final review 👍 |
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.
Looks great, thank you! The only comment from my side is that we should be more specific in notes that describe document-related functionality of each connector.
docs/components/connectors/out-of-the-box-connectors/amazon-bedrock.md
Outdated
Show resolved
Hide resolved
docs/components/connectors/out-of-the-box-connectors/amazon-s3.md
Outdated
Show resolved
Hide resolved
docs/components/connectors/out-of-the-box-connectors/amazon-textract.md
Outdated
Show resolved
Hide resolved
Thank you @chillleader -- this was going to be my lingering comment for you. I have tidied up these Connectors notes 👍 |
@christinaausley are you still planning for this to go live today? How can we support you? |
@akeller I feel this is in a good enough state to merge. If @chillleader has any lingering comments I can adjust in another PR -- just need an approval to merge here, and then I can do another docs release. |
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.
🚀 This looks great to me!
🧹 Preview environment for this PR has been torn down. |
Description
Relates to https://github.com/camunda/product-hub/issues/2555.
Document handling content for alpha-3.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).