Skip to content
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: notification wait for in send history #1194

Merged
merged 3 commits into from
Nov 13, 2024

Conversation

adityathebe
Copy link
Member

No description provided.

@adityathebe adityathebe force-pushed the feat/notification-wait-for-refactor branch from 53e3b5d to e9d6729 Compare November 11, 2024 15:36
@adityathebe adityathebe marked this pull request as draft November 11, 2024 15:46
Payload types.JSONStringMap `json:"payload,omitempty"`

// The duration to delay sending after its creation.
Delay *time.Duration `json:"delay,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be a timeout timestamp so that date math is not required on query - re the payload - I don't think we should be saving it, it should be re-hydrated from the config id / change it / check_id so that the notification sends out up to date info

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we do need to save the payload as it contains

  • resource id (config/component/check)
  • original event data to get the correct cel env.
  • recipient details

we will still do send out up-to date info.

@adityathebe adityathebe marked this pull request as ready for review November 12, 2024 07:12
@adityathebe adityathebe force-pushed the feat/notification-wait-for-refactor branch from a983fbf to b832b1e Compare November 13, 2024 04:30
@moshloop moshloop merged commit 6d646ff into main Nov 13, 2024
7 checks passed
@moshloop moshloop deleted the feat/notification-wait-for-refactor branch November 13, 2024 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants