-
Notifications
You must be signed in to change notification settings - Fork 819
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
feat: flow to add policies to access amplify resources from Lambda #1462
feat: flow to add policies to access amplify resources from Lambda #1462
Conversation
1b26bfc
to
c0e69ef
Compare
let actions = new Set(); | ||
|
||
crudOptions.forEach((crudOption) => { | ||
switch (crudOption) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the storage category we have 'create/update' option instead of both. I think it makes sense because it's illustrative of what's actually happening for the user, even though it's at the expense of slight inconsistency. Not a blocker for merging this but something that I think should be considered.
|
||
module.exports = { addWalkthrough, updateWalkthrough, migrate }; | ||
crudOptions.forEach((crudOption) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In askReadWrite function, we have 'create/update' instead of 'create' and 'update'.
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.