awslabs / awslabs/aws-deployment-framework

[Feature]: Support "Full clone" when using CodeCommit as the pipeline source

Open
#611 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
699
Forks
235
Avg merge
20h 53m
Merged PRs (30d)
7

Description

### Describe the feature

When using CodeCommit as the source for a pipeline, it would be useful to have available a new property called, for instance "full_clone" to support propagating the Git metadata across the stages.

### Use Case

For instance, in order to use checkov as a code scanner: https://aws.amazon.com/blogs/apn/using-aws-codebuild-and-bridgecrew-to-prevent-misconfigurations-in-aws-cloudformation-and-terraform/

The by default configuration make use of the git metadata to perform the tests.

### Proposed Solution

In CDK, set the codeBuildCloneOutput to true in the CodeCommit stage properties: https://docs.aws.amazon.com/cdk/api/v1/docs/@aws-cdk_pipelines.CodeCommitSourceOptions.html

### Acknowledgements

- [X] I may be able to implement this feature request

Contributor guide

Open the contributing guide

Research direction

Start with the CodeCommit pipeline source configuration and the CDK CodeCommitSourceOptions entry point named in the issue. Check how a new full_clone option should map to codeBuildCloneOutput; done when Git metadata is propagated across pipeline stages for CodeCommit sources and the checkov use case can access it.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.