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

Unique names for CDK test parameters and secrets #4

Open
fedonev opened this issue Nov 25, 2022 · 0 comments
Open

Unique names for CDK test parameters and secrets #4

fedonev opened this issue Nov 25, 2022 · 0 comments

Comments

@fedonev
Copy link
Owner

fedonev commented Nov 25, 2022

Add an option to append a unique identifier to AWS physical resource names.

Hardcoded parameter and secret names now cause resource collisions if the CDK test app is deployed more than once in an environment.
Multiple deploys would make parallel integration testing easier.

dummy-string-secret -> dummy-string-secret-8e3ac2

Add an optional Stack prop? That would let test callers determine whether a unique id is required or not.

We cannot simply use generated resource names. The local test cases depend on fixed naming in the test output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant