🧹 Skip permissions.json write when only timestamp changed#7071
Merged
Conversation
The permissions tool regenerates on every provider build, and the timestamp comes from the latest git commit. This causes a dirty diff even when no permissions actually changed. Compare the existing file content (ignoring generated_at) before writing to avoid noise. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![mondoo-code-review[bot]](https://avatars.githubusercontent.com/in/2834902?s=60&v=4){kind=small}
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Summary
.permissions.jsoncontent (ignoringgenerated_at) before writing(unchanged)Test plan
go run providers-sdk/v1/util/permissions/permissions.go providers/awsprints(unchanged)and produces no diff when permissions haven't changed🤖 Generated with Claude Code