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
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Import another module that uses Configuration, i.e. PSProfile.
Add a SecureString value to that module's configuration.
Import PSGSuite
Save the other module's configuration
Other module's configuration now shows the SecureString converter function as 'Secure' instead of the default function ConvertTo-SecureString set by Configuration itself.
Expected behavior
PSGSuite should use the same converter function that Configuration itself uses by default.
Screenshots
Additional context
This will need to be tested to ensure compatibility with existing PSGSuite configurations, as it stores most of it's values as SecureStrings.
The text was updated successfully, but these errors were encountered:
## 2.33.0 - 2019-09-26
* [Issue #236](#236)
* Fixed: Custom converter for Configuration metadata defaults to `ConvertTo-SecureString` as the preferred function instead of the custom `Secure`. `Secure` is still supported for backwards compatibility.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
ConvertTo-SecureString
set by Configuration itself.Expected behavior
PSGSuite should use the same converter function that Configuration itself uses by default.
Screenshots
Additional context
This will need to be tested to ensure compatibility with existing PSGSuite configurations, as it stores most of it's values as SecureStrings.
The text was updated successfully, but these errors were encountered: