Update script to verify go modules to match hashes of all files #1157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue found in the CI pipeline in #1146. In that instance, the CI initially failed indicating that the test vendor modules were not up to date, which also led to test failures in the CI.
This was because the
Verify-GoModules.ps1
script only validated that the code in the vendor directory of the package was unchanged. It did not, however, validate if the targetgo.sum
file matched the expected one for the code.go mod tidy
cleans up unnecessary references by removing their entries in thego.sum
file, thereby changing its contents. This could cause the main modules and the test modules to become out of sync.This PR addresses this issue by validating that all files in the target directory are as expected. This will include the go.mod and go.sum files.
Signed-off-by: Kathryn Baldauf [email protected]