Skip to content

PowerShell Core configuration #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

PowerShell Core configuration #111

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ad06465
PowerShell Core configuration
iSazonov Jan 25, 2018
b1b1df5
Fix typo.
iSazonov Mar 29, 2018
a209f4d
Address feedbacks
iSazonov Nov 21, 2018
5092fe4
Fix table
iSazonov Mar 21, 2019
6885504
Add Configuration defaults
iSazonov Mar 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 18 additions & 8 deletions 1-Draft/RFCnnnn-PowerShell-Configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ Comments Due: 2/25/2018

## Motivation

Consumers, developers, and enterpsise system administrators should be able to flexibly and conveniently configure PowerShell Core and applications based on it.
Consumers, developers, and enterprise system administrators should be able to flexibly and conveniently configure PowerShell Core and applications based on it.

The public PowerShell Core configuration API allows to use unified configuration means and to manage PowerShell-based applications in a consistent manner.
A public PowerShell Core configuration API would allow a unified way to manage PowerShell-based applications in a consistent manner.

## Specification

Expand All @@ -23,9 +23,9 @@ The public PowerShell Core configuration API allows to use unified configuration
- On Windows - Group Policy Objects (GPO), Group Policy Preferences (GPP) and settings files.
- On Unix - settings files.

The settings files have `Json` format.
The settings files have `JSON` format.

**Caution!** The settings files differ from `PowerShell Core` _profile_ files that are PowerShell scripts.
**Warning** The settings files differ from `PowerShell Core` _profile_ files, which are PowerShell scripts run at startup.

Configuration schemes allow to customize `PowerShell Core` in the most flexible way:

Expand Down Expand Up @@ -54,9 +54,19 @@ Scheme | Windows | Unix
GPO -> Computer Policy | HKLM\Software\Policies\PowerShellCore | /etc/powershell.config.json
GPO -> User Policy | HKCU\Software\Policies\PowerShellCore | See `Comment A` below
File -> Computer-Wide | %ProgramFiles%/PowerShell/powershell.config.json | /opt/Microsoft/powershell/powershell.config.json
File -> User-Wide | %APPDATA%/powershell.config.json | ~/powershell.config.json
File -> Application-Wide | $apphome/powershell.config.json | $apphome/powershell.config.json
File -> Application-Startup | pwsh -settingsfile `somepath/powershell.config.json` | pwsh -settingsfile `somepath/powershell.config.json`
File -> User-Wide | %APPDATA%/powershell.config.json | %XDG_CONFIG_HOME%/powershell.config.json
File -> Application-Wide | $apphome/powershell.config.json | $apphome/powershell.config.json

Defaults:

`%APPDATA%` - `C:\Users\useraccount\AppData\Roaming`

`%XDG_CONFIG_HOME%` - `HOME/.config`

#### Parameter `-settingsfile`

With `-settingsfile` parameter users can assign custom settings from the config file and overwrite user-wide and application-wide settings. Only users with elevated rights can overwrite computer-wide and user policy settings.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we are in lockdown mode, even elevated users should not be able to overwrite computer-wide settings

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only users with elevated rights can overwrite computer-wide and user policy settings.

I do not know how to formulate it right at the same time for Windows (GPO) and for Unix (only files).
In fact, the administrator always has the ability to change any setting.
Maybe remove the sentence at all?


#### Priorities for Regular settings in descending order

Expand Down Expand Up @@ -94,7 +104,7 @@ Software\PowerShellCore | - | -
| | UpdatableHelp | DefaultSourcePath | String
|Software\Policies\Microsoft\Windows\EventLog | ProtectedEventLogging | EnableProtectedEventLogging | DWORD

#### Json file settings format
#### JSON file settings format

```json
{
Expand Down Expand Up @@ -149,7 +159,7 @@ We could redesign `-settingsfile` startup parameter. If we'd support configurati

### Comment A

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
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

```json
{
Expand Down