-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat(endpoints): drop id prefix req endpoint secret key #16242
Conversation
9183bb4
to
aaf2ccc
Compare
aaf2ccc
to
85edc98
Compare
@@ -45,10 +45,10 @@ func (s Slack) Valid() error { | |||
if err := s.Base.valid(); err != nil { | |||
return err | |||
} | |||
if s.URL == "" && s.Token.Key == "" { | |||
if s.URL == "" { |
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.
token is not required for a url, if URL is "" it shoudl be an eror for slack, token shoudn't matter
Are we using the id prefix anywhere for lookups? I just want to be sure that this isn't going to be a breaking change. |
@jademcgough we aren't atm. We save teh entire secrets bit into the store, and never actualy use the notification id to look for the secret, the entire key is provided. It can be |
85edc98
to
9b1526b
Compare
the original design made the secrets unable to be reused, a bit to opinionated to be useful eleswhere. This relaxes that requirement so that secrets can be referenced here.
9b1526b
to
10c243f
Compare
same failing data race test from tasks/backend |
Closes #16240
Relaxes the rigid validation on endpoints to not require the id be prefixed.