Skip to content
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

Allow the user to set encrypted values directly #362

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

siegy22
Copy link
Contributor

@siegy22 siegy22 commented Mar 22, 2024

Before it was only possible to set an encrypted value by setting it in plain text. If the encrypted value was given, there was and endless re-apply happening because Splunk encrypts the values during boot time thus changing the value.

Now it's also possible to set the values by providing the encrypted value directly.

This Pull Request (PR) fixes the following issues

Fixes #284 (Maybe #197 ?)

Before it was only possible to set an encrypted value by setting it in plain text.
If the encrypted value was given, there was and endless re-apply happening
because Splunk encrypts the values during boot time thus changing the value.

Now it's also possible to set the values by providing the encrypted value directly.
@kenyon kenyon merged commit 9a1f36f into voxpupuli:master Mar 22, 2024
24 checks passed
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.

pass4SymmKey not read properly
2 participants