-
Notifications
You must be signed in to change notification settings - Fork 799
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
[backend/frontend] Add Outcome connector handling and introduce Webhooks #3707
Conversation
Can we have more inputs for this work ? Thank you :) |
Ok it's not a huge one, but you mean like that : [Redacted] |
outcome_connector: OutcomeConnector! | ||
outcome_connector_id: String! | ||
outcome_configuration: String! | ||
authorized_members: [MemberAccess!] @auth(for: [SETTINGS]) |
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.
could it be named authorizedMembers
? not to be confused with the stored field "authorized_members". Same for outcomeConnector
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 am waiting to discuss it with Julien to get know what is the rule of naming we want
opencti-platform/opencti-graphql/src/modules/notification/notification.ts
Show resolved
Hide resolved
Some update to make:
|
725e4e4
to
4cca592
Compare
42e7268
to
a5a4629
Compare
opencti-platform/opencti-graphql/src/modules/notification/notification.ts
Show resolved
Hide resolved
opencti-platform/opencti-graphql/tests/02-integration/04-manager/notificationManager-test.js
Show resolved
Hide resolved
...atform/opencti-front/src/private/components/settings/notifications/notifier/NotifierLine.tsx
Outdated
Show resolved
Hide resolved
...rm/opencti-front/src/private/components/settings/notifications/notifier/NotifierCreation.tsx
Show resolved
Hide resolved
} | ||
`; | ||
|
||
const NotifierPopover = ({ data, paginationOptions }: { data: NotifierLine_node$data, paginationOptions?: NotifierLinesPaginationQuery$variables }) => { |
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.
This is an issue we have everywhere in the platform :(
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.
Do we have an issue to track 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.
Nop, not have been a pain yet.
opencti-platform/opencti-graphql/src/manager/notificationManager.ts
Outdated
Show resolved
Hide resolved
da22a8c
to
c5a47e7
Compare
All comments have been answered |
7488a91
to
ad74af5
Compare
All good |
Tested locally and all good :) |
8110a26
to
d80d72f
Compare
Co-authored-by: Julien Richard <julien.richard@filigran.io>
Co-authored-by: Julien Richard julien.richard@filigran.io
Outcome connectors can be registered on the platform with a schema.
The admin can creates new Outcomes based on those connector and define specific fields based on their schema.
Specified members can use those outcomes in their triggers to receive their notifications