aws-control-tower-customizations
aws-control-tower-customizations copied to clipboard
CodeCommitBranchName doesn't affect initially created branch for CodeCommit during installation
Describe the bug Parameter CodeCommitBranchName can be set to change CodePipeline's CodeCommit branch to use. Unfortunately the CodeCommit repository itself will always set up its manifest etc. files on main branch.
A clear and concise description of what the bug is.
To Reproduce Install CfCT and change the CodeCommitBranchName parameter.
Expected behavior If changing the branch name for the Pipeline it should reflect installing the initial repository data into the same branch. Or at least the parameter should be renamed to tell that it only affects the CodePipeline's used branch name not the initially created on by CodeCommit.
Please complete the following information about the solution:
- 2.3.0
Additional context CloudFormation documentation for AWS::CodeCommit::Repository --> Code --> BranchName setting: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codecommit-repository-code.html#cfn-codecommit-repository-code-branchname
Thanks for bringing this up, @mdaehnert. I've made a backlog for your suggestion with the team.