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.
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
Goss should be able to assert against Windows Registry state #616
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@petemounce Any thoughts on this? |
I'm definitely in favour of being able to assert against it. The parallel approach works but due to its startup time injects about a second (unscientific approximate measure!) of overhead per assertion. |
Marked as approved. Windows and Mac are community supported, so I'll review/merge changes but I won't be the one making the change on this one. |
Describe the feature:
Goss should be able to assert against the state and contents of the Windows Registry.
Describe the solution you'd like
In order to properly support Windows configuration use cases, lots of things will need to be able to assert against registry keys. On *nix systems, you'd generally use a
file.contains
assertion against a configuration file, but the Windows equivalent is generally keys stored in the registry.Describe alternatives you've considered
The best I've got right now is that you can write a Powershell script that checks values in the registry and then outputs status, and then you wrap that script in a goss assertion. This is hacky, requires emplacing the script in the right place with the right permissions, etc, isolates some of the configuration to be checked separate from the rest, and just generally feels dirty.
The text was updated successfully, but these errors were encountered: