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

S3 Event Source for Lambda Functions in AWS Toolkit #355

Open
cbossie opened this issue Aug 14, 2023 · 1 comment
Open

S3 Event Source for Lambda Functions in AWS Toolkit #355

cbossie opened this issue Aug 14, 2023 · 1 comment
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@cbossie
Copy link

cbossie commented Aug 14, 2023

Describe the bug

S3 Event Sources do not show up in the "Event Sources" tab of the Lambda Function window in the toolkit.

To Reproduce

  1. Open any Lambda function using the AWS toolkit for VS.
  2. Choose the "Event Sources" tab
  3. Choose "+ Add"
  4. For "Source Type", select "Amazon S3". Select a bucket you want to use.
  5. Choose "OK"

Once you have done this, the event sources area is still blank. The event source is successfully applied (you can see it in the console). Plus if you try to re-add the same bucket, you get an error that you are trying to add a duplicate.

So the issue appears to be that it just does not show up in the list, other event sources, like SQS, do. The event source is created correctly in AWS.

Expected behavior

The expected behavior is that when you add an S3 event source, it will show up in the event sources area.

Screenshots

1 - Choose S3 Event Source
1 - Choose S3 Event Source In Toolkit

2 - What it looks like in Toolkit after S3 Event Source is Chosen
2 - What it looks like once in Toolkit after S3 Chosen

3 - S3 Event Source is Present in Console
3 - S3 Event Source is Present in Console

4 - Try to Readd S3 Event Source - Error
4 - Try to Readd S3 Event Source - Error

Computer (please complete the following information):

  • Windows Version: Windows 11 21H2 (22000.2295)
  • Visual Studio Version: VS 2022 Pro - 17.7.0
  • AWS Toolkit for Visual Studio Version: 1.42.0.0

Additional context

@cbossie cbossie added the bug We can reproduce the issue and confirmed it is a bug. label Aug 14, 2023
@rbbarad
Copy link
Contributor

rbbarad commented Aug 21, 2023

Thank you for bringing this issue to our attention. I was able to reproduce the issue and we are investigating further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants