You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I filed [#9632](https://github.com/PowerShell/PowerShell/issues/9632) on UpdatableHelp-DefaultSourcePath to make it allow User settings.
147
+
143
148
#### JSON file settings format
144
149
145
150
```json
@@ -196,17 +201,10 @@ A set of configuration settings in GPO scheme and file scheme for policy setting
196
201
We could attempt to resolve policy conflicts between PowerShell 7 policy and Windows PowerShell policy.
197
202
This would make the `Precedence for Policy settings` not just a simple list but a complex set of rules that would not be easily understood. See [this conversation](https://github.com/PowerShell/PowerShell/issues/9309?#issuecomment-480643922).
198
203
199
-
### Allow admins to overwrite computer-wide settings
200
-
201
-
In System Lock-down mode, we attempt to protect from the admin,
202
-
so allowing computer-wide or policy setting to be overwritten at the command-line is dangerous.
203
-
204
-
We could try to check for System Lock-down mode and
205
-
admin user and allow `-settingsfile` to overwrite computer-wide settings.
206
-
207
-
But, performing the system lock-down check this early would hurt startup performance.
204
+
### Allowing environment variable in the JSON
208
205
209
-
I don't recommend this approach.
206
+
A new RFC should be drafted about how to allow environment variables in the JSON.
207
+
This would allow consistent files across platforms.
0 commit comments