-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pivotal ID # 183688670: Structure Backend Notifications #693
Pivotal ID # 183688670: Structure Backend Notifications #693
Conversation
- Submit notifications independently for PMC / scheduler notifications - Remove "failed log" queues - Remove unused code
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.
Looking good please consider minotr comments
@@ -22,3 +24,8 @@ class DailyScheduling { | |||
var releaser: Boolean = true | |||
var exporter: Boolean = true | |||
} | |||
|
|||
class SlackConfiguration { |
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.
spring boot now support data class for configuration classes. So we can avoid the use latenit and use dataclass constructor binding. Check ApplicationProperties
@@ -6,7 +6,7 @@ import org.springframework.http.MediaType.APPLICATION_JSON | |||
import org.springframework.web.client.RestTemplate | |||
import org.springframework.web.client.postForEntity | |||
|
|||
class NotificationsSender( | |||
open class NotificationsSender( |
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 think rather than introduce extra classes and inhirantece we can use Spring @Qualifer to tag each bean diferently.
- Use Qualifier instead of inheritance - Use ConstructorBinding for the application properties
https://www.pivotaltracker.com/story/show/183688670