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

[I Made This]: Serverless multi-channel alerting solution based on user preferences #4804

Closed
1 task done
kubernoobie opened this issue Jul 23, 2024 · 4 comments
Closed
1 task done
Labels
community-content Community content to feature in the documentation content Content related tasks, e.g., blog posts, video, reusable artefact etc revisit Maintainer to provide update or revisit prioritization in the next cycle

Comments

@kubernoobie
Copy link

Link to your material

https://github.com/aws-samples/multichannel-app-to-person-alerting

Description

Implemented idempotency into my multi-channel alerting solution, using the message ID sent with the API request as the idempotency token/key.

Preferred contact

Orsolya B

(Optional) Social Network

No response

(Optional) Additional notes

No response

Acknowledgment

  • I understand this content may be removed from Powertools for AWS Lambda (Python) documentation if it doesn't conform with the Code of Conduct
@kubernoobie kubernoobie added the community-content Community content to feature in the documentation label Jul 23, 2024
Copy link

boring-cyborg bot commented Jul 23, 2024

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

@leandrodamascena
Copy link
Contributor

Hi @kubernoobie! Thanks for adding Powertools to your project. Can you tell us a little bit more about how Powertools helped you on this journey? Problems it solved and how Powertools makes the experience easier. We need to add some context and show to our customers the experience with Powertools.

Thanks

@leandrodamascena leandrodamascena added revisit Maintainer to provide update or revisit prioritization in the next cycle content Content related tasks, e.g., blog posts, video, reusable artefact etc labels Aug 11, 2024
@leandrodamascena
Copy link
Contributor

Hello! This issue has been without any response or interaction for a while! I am closing and please reopen it whenever you want.

Thank you

Copy link
Contributor

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-content Community content to feature in the documentation content Content related tasks, e.g., blog posts, video, reusable artefact etc revisit Maintainer to provide update or revisit prioritization in the next cycle
Projects
Status: Coming soon
Development

No branches or pull requests

2 participants