aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::CodeBuild::Project] - [expose scope prop to the construct.] - AWS code build webhook scope configuration for GitLab
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::CodeBuild::Project
### Resource name
_No response_
### Description
https://github.com/aws/aws-cdk/issues/34146
There's a discrepancy between the AWS CodeBuild API and the CloudFormation specification for the ScopeConfiguration property of AWS::CodeBuild::Project.
The CodeBuild API documentation (https://docs.aws.amazon.com/codebuild/latest/APIReference/API_ScopeConfiguration.html) shows that ScopeConfiguration should have both a name property and a scope property, with the latter being required and accepting values like 'GITHUB_ORGANIZATION', 'GITHUB_GLOBAL', or 'GITLAB_GROUP'.
However, the CloudFormation specification for AWS::CodeBuild::Project [ScopeConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codebuild-project-scopeconfiguration.html) only includes the name property.
This prevents users from properly configuring GitLab webhooks through CloudFormation or CDK, as it defaults to 'GITHUB_ORGANIZATION' without the ability to set it to 'GITLAB_GROUP'.
### Other Details
_No response_
Contributor guide
Research direction
The issue identifies AWS::CodeBuild::Project and its ScopeConfiguration property; start with the linked aws/aws-cdk#34146 issue and the AWS API and CloudFormation specification pages. Done means the scope property can be configured for values such as GITLAB_GROUP rather than defaulting to GITHUB_ORGANIZATION.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100