[aws-chatbot] L2 support for SlackChannelConfiguration

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:

const slackChannel = new chatbot.SlackChannelConfiguration(this, 'MySlackChannel', {
  slackChannelConfigurationName: 'test-channel',
  slackWorkspaceId: 'YOUR_WORKSPACE_ID',
  slackChannelId: 'YOUR_CHANNEL_ID', 
});

slackChannel.addLambdaInvokeCommandPermissions();
slackChannel.addNotificationPermissions();
slackChannel.addSupportCommandPermissions();
slackChannel.addReadOnlyCommandPermissions();

slackChannel.addToPrincipalPolicy(new iam.PolicyStatement({
  effect: iam.Effect.ALLOW,
  actions: [
    's3:GetObject',
  ],
  resources: ['arn:aws:s3:::abc/xyz/123.txt'],
}));

Other

Associate with #5020

cc @skinny85

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[luckily]

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:

1. L2 construct for CfnSlackChannelConfiguration of chatbot package.
2. L2 construct for CfnNotificationRule of codestarnotification package.
3. addNotification({...}) method of codebuild and codepipeline depend on above implements.

See also: #9680 #9682

[humanzz]

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