-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(pipelines): additionalInputs fails for certain repository names #15753
Comments
Hey @bodokaiser 👋🏻 I wasn't able to reproduce this with the given code (replaced connection arn and repos). Is that error throwing on the Source stage? Looking at the error I can see it starts with |
The error is thrown in the Do you repos contain dashes? My hypothesis is that it has something to do with dashes in the repository name which is either not formated correctly or too carefully validated. In our production setup, the editing the I am not exactly sure how this relates to the error I encounter in the minimal repository cdk-pipeline-invalid-inputs. With that error: it appears to me to be indeed related to the presence of dashes in the repository name as the |
Cause: dashes are valid in *artifact names* in CodePipeline, but are *not* valid in *secondary source names* in CodeBuild. Do a sanitization to the intersection of requirements between CodePipeline and CodeBuild. Fixes #15753.
…16017) Cause: dashes are valid in *artifact names* in CodePipeline, but are *not* valid in *secondary source names* in CodeBuild. Do a sanitization to the intersection of requirements between CodePipeline and CodeBuild. Fixes #15753. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…ws#16017) Cause: dashes are valid in *artifact names* in CodePipeline, but are *not* valid in *secondary source names* in CodeBuild. Do a sanitization to the intersection of requirements between CodePipeline and CodeBuild. Fixes aws#15753. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…ws#16017) Cause: dashes are valid in *artifact names* in CodePipeline, but are *not* valid in *secondary source names* in CodeBuild. Do a sanitization to the intersection of requirements between CodePipeline and CodeBuild. Fixes aws#15753. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
It appears to me that the
repository
parameter used withCodePipelineSource.connection
fails when used inadditionalInputs
of theCodePipeline
props.In our production setup, we get the following failure in the CodePipeline:

I tried reducing the problem to a minimal example and get a different error:
Reproduction Steps
Reproduction steps are summarized in the
README.md
of cdk-pipeline-invalid-inputsWhat did you expect to happen?
A successful build.
What actually happened?
In our production environment
CodePipeline
raises an error that the input source name is invalid (containing dashes?) while in the minimal example the synth command fail.Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: