-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
ref(slack): Remove slack-v2 creds and usage #23587
Conversation
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.
LGTM, I'll approve once the other PR is merged just so we don't accidentally merge this first
e4b90bf
to
2f33180
Compare
Confirming here that the following credentials have been updated:
The |
|
||
resp = self.client.post("/extensions/slack/action/", data=payload) | ||
resp = self.client.post("/extensions/slack/action/", data=payload, **headers) |
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.
can't seem to get the signatures to match when I actually pass in the correct headers :(
8409f50
to
cfb2739
Compare
* ref(slack): Remove slack-v2 creds and usage * update slack requests tests * dont need verification token * add broken test * mock signing secret
Once #23545 is merged and deployed, we will have removed basically all the functionality for slack workspace apps. The last piece is the app itself, and it's credentials.
IMPORTANT: This PR should only be merged AFTER we have updated our slack-v2 credentials to replace our slack credentials.
We started out with one slack app, our now deprecated workspace app. The credentials for this app are:
We then introduced a new Slack integration, the bot app. The credentials for that app are:
Now there is actually a third type of app which is a older bot app, this kind of bot app may still be used by self hosted sentry users, and may be using the
slack.verification-token
instead of the signing secret (though they should probably update their app to use the secret). But anyway this is the reason we need to keep that option, although sentry SaaS will not need it.mini clean up: we don't use the option
slack.legacy-app
anymore, so getting rid of itSide Note: I'm mocking out the signing secret check in the endpoint tests because I couldn't get the payloads to match for some reason,I want to come back to this, but it isn't any worse that what it was before because these tests used the verification token which we don't use anymore