AWS::CodeBuild::Project - VpcConfig
1. Title
AWS::CodeBuild::Project-VpcConfig
2. Scope of request
Removing the VpcConfig property from the template should remove it from the CodeBuild project, which it currently does not.
3. Expected behavior
In Update, removing the VpcConfig attribute should update the CodeBuild project and remove its VPC configuration.
4. Suggest specific test cases
Create AWS::CodeBuild::Project with VpcConfig specified, then try to remove it. Success: Physical CodeBuild project has its VpcConfig removed Fail: Template/stack gets updated without any real changes to the CodeBuild project - becoming out of sync.
5. Helpful Links to speed up research and evaluation
https://docs.aws.amazon.com/codebuild/latest/APIReference/API_UpdateProject.html
6. Category (required) - Will help with tagging and be easier to find by other users to +1
- Developer Tools (CodeStar, ...)
7. Any additional context (optional)
using VpcConfig: {} as a workaround should fix this issue.
I was affected by this as well, manually removing the CodeBuild project from the VPC in the env part of the console did the trick and didn't break my CloudFormation stack. I hit this bug using CDK.
Hi,
Isn't it a bug from CloudFormation ?
This also applies to SecondaryArtifacts