This repository was archived by the owner on Sep 3, 2025. It is now read-only.
Automatically engage users in Signal data with Signal Engagements and confirm behavior #3274
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevgliss
approved these changes
Apr 17, 2023
| callback_id=SignalEngagementActions.deny_submit, | ||
| private_metadata=context["subject"].json(), | ||
| blocks=[ | ||
| Section(text="Confirm that this is not expected and that the activity is suspicious."), |
Contributor
There was a problem hiding this comment.
Should we add some context to what this means? e.g. an incident will be created | the security on-call will be engaged?
Contributor
Author
There was a problem hiding this comment.
Will add, I haven't configured the auto-resolve/escalate functionality yet
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I still need to test this w/ MFA, write tests, and clean this up.