This PR adds support for setting up a new deployment of PCM without deploying a new Cognito user pool instance, so that a previously deployed user pool could be used instead.
This is achieved through the use of new parameters (easily obtainable from CloudFormation console) to be passed at stack creation time.
Changes
Introduced external cognito parameters
adjusted parameter descriptions
Changelog entry
How Has This Been Tested?
manual tests on multiple deployments on my personal account
References
PR Quality Checklist
[ ] I added tests to new or existing code
[ ] I removed hardcoded strings and used our i18n solution instead (see here)
[x] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
[ ] I checked that infrastructure/update_infrastructure.sh runs without any error
[ ] I checked that npm run build builds without any error
[x] I checked that clusters are listed correctly
[x] I checked that a new cluster can be created (config is produced and dry run passes)
[x] I checked that login and logout work as expected
Description
This PR adds support for setting up a new deployment of PCM without deploying a new Cognito user pool instance, so that a previously deployed user pool could be used instead. This is achieved through the use of new parameters (easily obtainable from CloudFormation console) to be passed at stack creation time.
Changes
Changelog entry
How Has This Been Tested?
References
PR Quality Checklist
i18nsolution instead (see here)npm run buildbuilds without any errorIn order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.