-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
Adding ISR page to already created app doesn't update the IAM policy #1510
Comments
I am having the exact same issue here! |
As pointed here #1098 (comment)
I guess it was a similar issue |
Yea, I guess for now you need to manually update the default lambda policy =/ I guess it should be this code that needs to be updated to update the policy: serverless-next.js/packages/serverless-components/aws-lambda/src/utils.ts Lines 273 to 288 in 8269ee8
|
Issue Summary
In a scenario where my application doesn't have ISR yet and all the resources were previously provisioned, by adding a page with ISR all the new resources get created but the IAM role of default lambda doesn't get updated.
Actual behavior
Adding new ISR page doesn't work.
Expected behavior
Adding new page feature should update the IAM policy
Steps to reproduce
Screenshots/Code/Configuration/Logs
Logs:
Policy not updated:
If I delete the IAM role it will get re-created but this time with the right policy:
Only then with the new policy it starts to work again
Versions
Additional context
Checklist
latest
oralpha
@sls-next/serverless-component
release version, which may have already fixed your issue or implemented the feature you are trying to use. Note that the oldserverless-next.js
component and theserverless-next.js
plugin are deprecated and no longer maintained.The text was updated successfully, but these errors were encountered: