Fix: ConvertTo-IcingaSecureString exceptions because of not being pre-loaded #223
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LordHepipud
force-pushed
the
fix/convertto_icinga_secure_string_is_not_preloaded
branch
from
79983e5 to
0da3195
Compare
LordHepipud
deleted the
fix/convertto_icinga_secure_string_is_not_preloaded
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With updating Icinga for Windows to v1.4.0, there is an issue with plugins using [Secure.String] variables. By default, we convert string values with the function
ConvertTo-IcingaSecureStringto a [Secure.String] for PowerShell for better usage. Because of the plugin execution change, this function is no longer available withUse-Icinga -MinimalThis only affects environments with udpated configuration
Fixes #222