This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt in trying to fix the function's predefined role current issues for good.
With a solution like this one, we are now always having a iam.Role in a Function. No more issue with trying to access an undefined role from another component.
Instead of considering role to be undefined when predefined role is passed, we are now referencing the actual role. So the role will either be a reference or we create it if not passed.
Thats the idea but please let me know if I miss some important context on why it should not be done like this.
I have tried this solution with ApiGatewayV1 and NextJS server function. They now both work fine even though it didnt work in the past.
Closes sst/sst#4180