[Bug]: AWS-side changes to CodeBuild project causes secondary_sources
block diffs with aws_codebuild_project
#37052
Labels
bug
Addresses a defect in current functionality.
service/codebuild
Issues and PRs that pertain to the codebuild service.
service/iam
Issues and PRs that pertain to the iam service.
Terraform Core Version
1.7.5
AWS Provider Version
1.46.0
Affected Resource(s)
aws_codebuild_project
Expected Behavior
While working on and validating a fix for #36987, many acceptance tests failed due to some unexpected differences, one of which is related to attributes in the
secondary_sources
config block. See error message below. It seems that after a reason update (most likely on server side), the provider started reporting differences with the configuration block for attributes includinggit_clone_depth
,insecure_ssl
, andreport_build_status
. The diff also seems to be replacing the blocks instead of updating them with the attributes, maybe it's another point of interest. Since one of the attributes arereport_build_status
, I wonder if it's related to #37051 as well. On quick glance I didn't see any recent code changes to the resource code that'd have caused this. I would have fixed this myself (like set default values in the resource schema) but I am not sure what the best approach would be. Thus I'd like someone more experienced to assist with this fix.Acceptance tests should not fail or generate diff.
Actual Behavior
Many acceptance test cases failed.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Simply run acceptance tests for CodeBuild the codebuild package, for example:
make testacc PKG=codebuild TESTS=TestAccCodeBuildProject_SecondarySources_codeCommit
Alternatively, extract one of the test cases, such as the configuration above, and apply it once to create the resource, then apply it again to see the unexpected update.
Debug Output
n/a
Panic Output
n/a
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: