feat(policy): add runtime baseline conflict controls#1629
Conversation
|
🌿 Preview your docs: https://nvidia-preview-pr-1629.docs.buildwithfern.com/openshell |
93e19ff to
8310d74
Compare
Signed-off-by: Evan Lezar <elezar@nvidia.com>
Signed-off-by: Evan Lezar <elezar@nvidia.com>
8310d74 to
f7ff308
Compare
PR Review StatusValidation: this is maintainer-authored, project-valid policy/sandbox work for #1486, adding explicit runtime baseline conflict controls while preserving a default-deny posture for device-node promotion. Review findings:
Docs: Fern policy reference and sandbox policy docs were updated; no navigation change appears needed. Next state: |
|
Label |
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Summary
Adds explicit filesystem policy controls for runtime baseline conflicts as an alternative to #1522. The default permits
/procread-only to read-write promotion for runtime baseline needs, while other conflicts such as device-node promotions require explicit policy opt-in.Related Issue
Resolves #1486
Alternative to #1522.
Changes
filesystem_policy.runtime_baseline_conflicts.read_only_to_read_writewithreject_unlisted,promote_all, andreject_allmodes.reject_unlistedwith/procinallow_promotion.Testing
mise run pre-commitpassesChecklist