Closed thelegendtubaguy closed 2 months ago
Oh my userPool
is a Pulumi resource, not an SST Ion component. I'm going to guess that's it :D
I have switched to the very newly released CognitoUserPool
SST component and it still isn't linking. Maybe I'm just too early to using it? It is not listed under link
in state edit
.
Hey @thelegendtubaguy what r u trying to do w/ the user pool in ConnectionFunction?
It'd be nice to access the user pool ID. The function is specifically doing list users, update user attributes, and add user to groups.
I was able to work around this by specifying permissions on the function and setting the user pool id as an env var for now.
Added in v0.0.325.
Now when u link CognitoUserPool
, you can access Resource.MyUserPool.id
, and the function has cognito-idp:*
permission on the user pool arn.
Feel free to reopen if this doesn't work for you.
Awesome! Thank you!
I'm following the monorepo design such that my folder structure looks like this:
I have several different functions in my functions package, each with mostly unique "links" to other resources. I've defined one like so:
However when I ran this lambda I was told that "UserPool" was not linked (the resource name on
userPool
). Thesst-env.d.ts
is mysteriously missing any reference to "UserPool".Do I need to have the same
link
on every function to get this to show up? I don't really want to give permissions to my user pool to every function if they don't need it. Thanks!And thank you for introducing me to Pulumi. Working with this has been such a dream compared to CDK.