Skip to content

Add Installer-EXE logic for Windows-Based targets#5

Merged
ferricoxide merged 20 commits into
mainfrom
AddWindows_EXE
Apr 9, 2026
Merged

Add Installer-EXE logic for Windows-Based targets#5
ferricoxide merged 20 commits into
mainfrom
AddWindows_EXE

Conversation

@ferricoxide
Copy link
Copy Markdown
Member

Implements both an installation/configuration state and a "clean" state. Both take care of:

  • Assuring appropriate installation-status of the Chrome Browser
  • Assuring appropriate installation-status of the Chrome Browser policy-components

Additionally, the "bits" are parameter-driven enough that they should provide additional flexibility beyond the explicitly tested-for usages.

*   Install security-related registry-keys (if expressly selected for)
    * HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\HomepageLocation
    * HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ManagedBookmarks
    * HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ManagedBookmarks
    * HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update\ManagedBookmarks

*   Stage and nstall ADMX and ADML policy files:
    * C:\Windows\PolicyDefinitions\en-US\chrome.adml
    * C:\Windows\PolicyDefinitions\google.admx
    * C:\Windows\PolicyDefinitions\chrome.admx
The new, stoopidly-long URLs *should* be more reliable ...At least until
Google decides to "improve" things, again
...and return to original state if it changed
Attempt to resolve a conflict between how Salt likes paths and how
PowerShell likes paths when running as LocalSystem
Also, allow the "Set-ItemProperty" logic to not bomb-out if a registry-key
is missing/null
Use an externalized uninstallation script to provide better reliability
and "chattier" output about the script's activities
Use parameters so we can try to make this more-flexible via Pillar-
hosted content-specifications
using a non-iterated `names` construct isn't adequately robust and fails
on Windows targets
Damn you, YAML, and your padding-sensitivity!
While we're here, update to reflect new parameter maps
@ferricoxide ferricoxide force-pushed the AddWindows_EXE branch 5 times, most recently from 37b49e9 to 04e20f6 Compare April 9, 2026 18:10
@ferricoxide ferricoxide merged commit c32763a into main Apr 9, 2026
5 of 7 checks passed
@ferricoxide ferricoxide deleted the AddWindows_EXE branch April 9, 2026 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant