@aws-cdk/pipelines. CdkPipeline: Enable multiple sources

[brimock]

Currently we can only specify a single source repository for a CdkPipeline, however it would be cleaner to enable us to store different parts of our application in different repositories.

Use Case

I have infrastructure and application code in different repos, and would like to have them deployed within the same pipeline.

Proposed Solution

Change sourceAction to be an array of source actions, i.e. sourceActions

This is a 🚀 Feature Request

[bodokaiser]

Related #14490

[rix0rrr]

Will be addressed by #12326, closing early as duplicate to keep tracking more manageable.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[robert-hanuschke]

@rix0rrr #12326 is merged now but I think it does not include multiple sources (at least I don't see it in the documentation and couldn't configure it in v1.125.0). Should this be reopened?

[bodokaiser]

@robert-hanuschke You find additionalInputs in ShellStepProps.

This is also explained in the additional inputs section:

const prebuild = new ShellStep('Prebuild', {
  input: CodePipelineSource.gitHub('myorg/repo1'),
  primaryOutputDirectory: './build',
  commands: ['./build.sh'],
});

const pipeline = new CodePipeline(this, 'Pipeline', {
  synth: new ShellStep('Synth', {
    input: CodePipelineSource.gitHub('myorg/repo2'),
    additionalInputs: {
      'subdir': CodePipelineSource.gitHub('myorg/repo3'),
      '../siblingdir': prebuild,
    },

    commands: ['./build.sh'],
  })
});

and yes, I agree that such a great feature deserves more visibility.

[robert-hanuschke]

@bodokaiser ah, so the additional inputs defined in that way also trigger the pipeline (e.g. if nothing changed in myorg/repo1 but in myorg/repo3)? I interpreted that section in the way that the trigger still would only be morg/repo1 but once that fires it additionally loads repo2 and repo3 for supplementary data in support of repo1's changes.

If I thought wrong there and changes to repo2 and repo3 also fire the pipeline - very cool, will try that!

[bodokaiser]

@robert-hanuschke I think so, in the ShellStep constructor they get the same treatment.