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
slack-bot: handle interactions by filing issues #1264
slack-bot: handle interactions by filing issues #1264
Conversation
2bd0842
to
9d75a01
Compare
@alvaroaleman do you know how this is supposed to work? |
6bff56a
to
d3efa7c
Compare
Would you mind adding a README with a short architectural description? It could be as simple as a list of links to the relevant API documentation if it's good. I found it hard to even begin reviewing the interaction code without knowing what process it implements. It would also benefit other reviewers and future-us during maintenance. |
a7d4e70
to
1e0090e
Compare
This implements DPTP-1476 |
d18bcc4
to
399e367
Compare
With this patch, the test platform Slack integration now knows how to respond to a number of shortcut actions from users, opening dialogs that prompt them for information in order to open issues on the DPTP Jira board. The following types of issues are supported: - bugs - consulting requests - feature requests - incident tracking cards Input validation is achieved with custom validation on submissiosn as well as built-in Slack modal features; users have interactive flows to provide them feedback on the inputs and allow them to open bugs against this tool if we run into unexpected issues. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
399e367
to
0b784b9
Compare
Posting the reply here for other reviewers: https://api.slack.com/surfaces/modals/using. |
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 haven't gone line-by-line (surprise!) but the structure makes sense to me and I think I would be able to maintain and extend this if needed, so LGTM.
One thing that I did not like though are the tests with huge JSON blobs as inputs, I don't think they serve their purpose well, although I see how it's not really easy to make the inputs trivial and easy to read. Could we have some builder for them? And if not, I think we should at least use fixtures.
pkg/slack/util.go
Outdated
@@ -0,0 +1,4 @@ | |||
package slack | |||
|
|||
// CoreOSHost is the hostname for the CoreOS Slack |
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.
nit: actually not a hostname but URL
/test e2e |
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
7440799
to
d87a1b8
Compare
All tests use fixtures, responded to all comments. @alvaroaleman @petr-muller |
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.
✔️
/hold Fol Alvaro to have a chance |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, stevekuznetsov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
@stevekuznetsov: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/test e2e |
/retest Please review the full test history for this PR and help us cut down flakes. |
With this patch, the test platform Slack integration now knows how to
respond to a number of shortcut actions from users, opening dialogs that
prompt them for information in order to open issues on the DPTP Jira
board. The following types of issues are supported:
Input validation is achieved with custom validation on submissiosn as
well as built-in Slack modal features; users have interactive flows to
provide them feedback on the inputs and allow them to open bugs against
this tool if we run into unexpected issues.
Signed-off-by: Steve Kuznetsov skuznets@redhat.com