Deprecate the encr_password field from storage/passwords
#695
+21
−18
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
szykol
approved these changes
Jan 19, 2026
Ickerday
changed the title
encr_password field from storage/passwords
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Splunk is deprecating the
encr_passwordfield from/services/storage/passwords. We need to mark the field as deprecated to instruct users to move away from it.More info: https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.2/access-endpoints/access-endpoint-descriptions#storage.2Fpasswords
NOTE: Depending on whether we decide to release the AI module as a separate package or not, I'll need to pull in either
deprecation,deprecatedor else to solve Python not having a deprecation mechanism built-in before 3.13.