You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✕ Failed
Error: "nodes.role" is not available when a pre-existing role is used.
at Object.get role [as role] (file:///my-project/.sst/platform/src/components/aws/function.ts:1596
:17)
at /my-project/.sst/platform/node_modules/@pulumi/output.ts:758:57
at Array.some (<anonymous>)
at impl (/my-project/.sst/platform/node_modules/@pulumi/output.ts:758:37)
at containsUnknowns (/my-project/.sst/platform/node_modules/@pulumi/output.ts:743:12)
at /my-project/.sst/platform/node_modules/@pulumi/output.ts:180:84
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Promise.all (index 2)
The text was updated successfully, but these errors were encountered:
Actually, we are facing the same issue in my company. It is the last blocker we have before to move all our stack to SST. I hope this issue will find a solution 🤞
I retried with my current version of SST (3.0.73) and still didnt work. But I tried upgrading to latest version (3.1.35) and it worked!
So I guess it was fixed indirectly.
I still wonder if my PR is worth checking as it should prevent any potential issue like this in the future by referencing the role used when not creating one. But other than that, we can close this issue.
For ApiGatewayV2, it works:
For ApiGatewayV1, it does not work:
Error:
The text was updated successfully, but these errors were encountered: