-
Notifications
You must be signed in to change notification settings - Fork 115
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
[connectors] Upsert and backfill Confluence spaces as data_source_folders
#9402
Conversation
6129354
to
d44c317
Compare
await upsertFolderNode({ | ||
dataSourceConfig, | ||
folderId: internalId, | ||
parents: [internalId], | ||
title: confluenceSpace?.name ?? confluenceId, | ||
}); | ||
|
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.
ok to make the user wait for this operation to complete?
we could technically do this in the workflow but it leads to higher risks of having the table confluence_spaces and the data_source_folders out of sync IMHO
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.
I'd actually rather do it in the activities, that's where we upsert in core
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.
alright, doing that 👍
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 good, left a few coms 👍
Mostly, I don't get how we have 2 levels of hierarchy in our confluence, and how this is handled by the parents array?
import { concurrentExecutor } from "@connectors/lib/async_utils"; | ||
import { |
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.
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.
these are pages, which are not folders but can be parents to other pages
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.
does this break anything regarding kwsearch?
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.
as per IRL: we're good 👍
await upsertFolderNode({ | ||
dataSourceConfig, | ||
folderId: internalId, | ||
parents: [internalId], | ||
title: confluenceSpace?.name ?? confluenceId, | ||
}); | ||
|
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.
I'd actually rather do it in the activities, that's where we upsert in core
await deleteFolderNode({ dataSourceConfig, folderId: internalId }); | ||
|
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.
@philipperolet would you rather delete from core first and then from connectors or the opposite? no strong opinion 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.
as per IRL: core first 👍
@philipperolet I moved the calls to front -> core to activities, can you check again please? 🙏 |
Description
data_sources_folders
, I also get the nodes indata_sources_nodes
withmime_type
application/vnd.dust.folder
.Risk
Deploy Plan