Proceed with execution even if policy file invalid - #76
Merged
Conversation
Bhaskar Brahma (D1v38om83r)
approved these changes
Jul 14, 2026
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
3 participants
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.
Overview:
Part of the constrained extensions code involves reading a policy file (the file that contains the policy rules for the extension). Previously, if the file was corrupt (invalid JSON, empty/cleared file), then the extension would log the error and exit.
However, all the constrained extensions feature work is new, and we should err on the side of caution. Thus, for now if the policy file is invalid, we log the error but continue execution with no policy applied. This change matches the code changes made here in RCv2 Windows.
PR includes: