Repository navigation
fix: the Organization Policy Exceptions note names the policies it counts - #21
Merged
Merged
Conversation
…unts The Informational line about the policies set below that weaken no guardrail showed an empty constraint (—) and a bare count, which read like a finding with a hole in it. It now names them: the constraint when there is one (else how many), the resource when there is one (else how many), Below 'set — weakens nothing', and the Detail lists each policy on its resource. The Below column of the Organization Policies table skips the note by its empty Above.
prateekgsingh
added a commit
that referenced
this pull request
Nov 20, 2026
After a day of rc.1 on the scheduled scans (clean): VERSION and terraform/versions.tf read 20.0.0-rc.2; the notes section is headed v20.0.0-rc.2 and gains the line on the Organization Policy Exceptions note naming its policies (#21); the roadmap row says so.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Found by the owner in the v20.0.0-rc.1 report: the second row of Organization Policy Exceptions had an empty constraint. It is the v19.3 Informational line about the policies set below that weaken no guardrail — a note, not a finding — but with
—in four columns and a bare count it read like a finding with a hole in it.Now the line names what it counts: the constraint when there is one (else "N constraints"), the resource when there is one (else "N resources below"), Below set — weakens nothing, Issue "N policies set below that weaken no guardrail.", and the Detail lists each
constraint on resource(up to ten). On the reference organization it readsvertexai.allowedPartnerModelFeaturesonprojects/stark-argolis. The Organization Policies table's Below column skips the note by its empty Above.Tests updated; suite 1,347 green. Ships as
v20.0.0-rc.2tomorrow after the first scheduled scans.