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
@@ -191,15 +191,7 @@ I filed [#9632](https://github.com/PowerShell/PowerShell/issues/9632) on Updatab
191
191
"PoliciesSettings": {
192
192
...
193
193
}
194
-
},
195
-
196
-
"OtherPowerShellApplication": {
197
-
"RegularSettings": {
198
-
...
199
-
},
200
-
"PolicySettings": {
201
-
...
202
-
}
194
+
}
203
195
}
204
196
```
205
197
@@ -214,37 +206,10 @@ The main purpose of describing the alternative is to describe why it should not
214
206
215
207
#### Description
216
208
217
-
We could attempt to resolve policy conflicts between PowerShell 7 policy and Windows PowerShell policy.
209
+
PowerShell could attempt to resolve policy conflicts between PowerShell 7 policy and Windows PowerShell policy.
218
210
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).
219
211
220
212
### Allowing environment variable in the JSON
221
213
222
214
A new RFC should be drafted about how to allow environment variables in the values in the JSON.
223
215
This would allow consistent files across platforms.
224
-
225
-
### Comment A
226
-
227
-
Mainly for Unix we'd add `Users` section to computer wide JSON file (`/etc/powershell.config.json`) to allow administrators set policies and regular settings on user level base
0 commit comments