-
Notifications
You must be signed in to change notification settings - Fork 66
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
[BUG] Only one PDKPipeline can be created per account/region #239
Comments
@cogwirrel Agree that |
Just had a quick look and yes, we should also prefix For this one we'll have to make sure our internal tool points to the new export name as we automate writing the sonar qube token to that secret :) |
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. |
Why is this even an export and not simply an output? I can't find anything that imports the value. I searched all of GitHub for If we make this a simple output, it will solve this problem. |
I see examples of How are developers using these values? |
The sonar qube secret export is used by our internal tool for bootstrapping new prototyping projects :) I'll send you a link! As far as I know the code repo url is exported just so it's printed after a CDK deploy, so that users know what to put in the |
The pipeline package was exporting `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` which meant the stack could only be deployed once per region. Nothing seems to be importing these exports. After discussing with the maintainers, we determined that simple outputs are sufficient. BREAKING CHANGE: `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` are no longer CloudFormation exports. Any systems that relied on those being exports will need to be updated to look up the output value by the stack name. fix aws#239
The pipeline package was exporting `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` which meant the stack could only be deployed once per region. Nothing seems to be importing these exports. After discussing with the maintainers, we determined that simple outputs are sufficient. BREAKING CHANGE: `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` are no longer CloudFormation exports. Any systems that relied on those being exports will need to be updated to look up the output value by the stack name. fix aws#239
The pipeline package was exporting `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` which meant the stack could only be deployed once per region. Nothing seems to be importing these exports. After discussing with the maintainers, we determined that simple outputs are sufficient. BREAKING CHANGE: `CodeRepositoryGRCUrl` and `SonarqubeSecretArn` are no longer CloudFormation exports. Any systems that relied on those being exports will need to be updated to look up the output value by the stack name. fix #239 Co-authored-by: Adrian Dimech <51220968+agdimech@users.noreply.github.com>
Describe the bug
See: #235
The
exportName
for theCodeRepositoryGRCUrl
is hardcoded and so conflicts with a second deployment ofPDKPipeline
.Expected Behavior
Able to deploy multiple
PDKPipeline
constructs in the same account/regionCurrent Behavior
Reproduction Steps
Deploy more than one
PDKPipeline
, either in the same app or as separate apps.Possible Solution
Include
props.repositoryName
in the export name since this is already a unique name.Additional Information/Context
No response
PDK version used
0.12.4
What languages are you seeing this issue on?
Typescript, Java, Python
Environment details (OS name and version, etc.)
OSX
The text was updated successfully, but these errors were encountered: