-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[aws-chatbot] L2 support for SlackChannelConfiguration #9679
Comments
Hey @luckily, it's great that you're looking into this because between @Stacy-D and myself, we too were keen to get an L2 construct very similar to what you proposed above in #8636 (comment). Just to avoid duplication of efforts, I wanted to connect to know if you're planning to progress this soon with a contribution? Our initial plan was to try to do that sometime over next week but if you're going to be doing that we'd happily step back and await for your contribution :) |
Hi @humanzz, I'm so happy that you have similar problem. I have some plans to resolve this issue and this is my proposed. These include:
|
@luckily Thanks for acting super quickly on this... we can't wait till this gets merged/released :) |
It’s quite similar; I added a couple of comments. Pinging @Stacy-D as she was the one actually working on our version if she has any additional comments |
… of chatbot. (#9702) I am ready for the first run. Support L2 construct for SlackChannelConfiguration of chatbot. 1. add L2 construct 2. add unit tests 3. add integration test 4. update package.json Resolves: #9679 cc @skinny85 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Currently there's only L1 resources in
CfnSlackChannelConfiguration
of aws-chatbot.Let's create L2 construct support.
Use Case And Proposed Solution
It's just like we create slack channel configuration via AWS web console.
There is pseudocode as below:
Other
Associate with #5020
cc @skinny85
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: