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

Allow reconfigure EventSourceMapping after running amplify add function #13322

Closed
2 tasks done
yaquawa opened this issue Oct 11, 2023 · 2 comments
Closed
2 tasks done
Labels
duplicate If marked with duplicate, issue will be closed & original will be added for traceability functions Issues tied to the functions category pending-triage Issue is pending triage

Comments

@yaquawa
Copy link

yaquawa commented Oct 11, 2023

Is this feature request related to a new or existing Amplify category?

function

Is this related to another service?

No response

Describe the feature you'd like to request

When using Amplify to create a Lambda function with event triggers, it's possible to specify the associated DynamoDB tables during the initial setup. However, there might be scenarios where you need to reconfigure or update the event source mappings to associate the Lambda trigger with different tables. This issue explores how to achieve this reconfiguration.

Describe the solution you'd like

Users should be able to reconfigure the event source mapping for a Lambda function created through Amplify, allowing them to associate the function with different DynamoDB tables. The process for updating the event source mappings after the initial amplify add function command should be documented clearly.

Describe alternatives you've considered

x

Additional context

Where is what the doc says, but you can't "reconfigure" this after the initial setup.
image

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request

Would this feature include a breaking change?

  • ⚠️ This feature might incur a breaking change
@yaquawa yaquawa added the pending-triage Issue is pending triage label Oct 11, 2023
@ykethan
Copy link
Member

ykethan commented Oct 11, 2023

Hey @yaquawa, thank you for reaching out. The feature is currently being tracked on #4038. Please feel free in adding a thumbs up on the issue.

Closing the issue as duplicate.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please 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.

@ykethan ykethan added functions Issues tied to the functions category duplicate If marked with duplicate, issue will be closed & original will be added for traceability labels Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate If marked with duplicate, issue will be closed & original will be added for traceability functions Issues tied to the functions category pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

2 participants