Skip to content
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

aws-qa-appsync-opensearch: Make congnito user pool id as optional input #439

Open
1 of 2 tasks
saikatak opened this issue May 9, 2024 · 1 comment
Open
1 of 2 tasks
Labels
backlog enhancement New feature or request

Comments

@saikatak
Copy link
Contributor

saikatak commented May 9, 2024

Describe the feature

Currently the module aws-qa-appsync-opensearch authenticates GraphQL APIs using cognito user as primary authentication mode and IAM as additional authentication mode.

This module is requiring cognito user pool id as mandatory input parameter making the consumer of this module create user pool explicitly and provide the user pool id which would take away the simpleness of the module. Making cognito user pool id as optional(and falling back to IAM authentication if no user pool is provided) would help to avoid the additional effort required to create user pool out side of this module.

Use Case

When using this module for simple and sample POCs , we are required to create a cognito user pool and user pool application client and then use it along with this module.

Proposed Solution

Make cognito user pool id as optional and fall back to IAM authentication if no cognito user pool is is passed

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change
Copy link
Contributor

github-actions bot commented Jul 9, 2024

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

@github-actions github-actions bot added the stale label Jul 9, 2024
@krokoko krokoko added backlog and removed needs-triage This issue or PR still needs to be triaged. stale labels Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants