Open mawallace opened 3 weeks ago
Hey @mawallace, thanks a lot for this enhancement idea! I think this would be a good addition to the provider. It would need to be added to the upstream provider first before we can pull it into pulumi-aws. Can you open a feature request here as well please: https://github.com/hashicorp/terraform-provider-aws/issues.
The endpoints follow a fixed pattern, so in the meantime you could do the following to construct it (typescript example):
const region = aws.getRegionOutput({}).name;
const endpoint = pulumi.interpolate`https://cognito-idp.${region}.amazonaws.com/${userPool.id}`
Describe what happened
A Cognito user pool's endpoint should be available via the
getUserPool
data source. It seems like a common use case to have a user pool located in one stack, and then an API with a Cognito-based JWT authorizer that needs the endpoint in another stack (see the example below).Right now, you have to either
getUserPool
Sample program
This is what I want to be able to do.
However, the
endpoint
field is not available from thegetUserPool
result.Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).