Document how to use GPG encrypted pillar within another pillar file#63504
Merged
dwoz merged 3 commits intosaltstack:masterfrom Jan 28, 2026
Merged
Document how to use GPG encrypted pillar within another pillar file#63504dwoz merged 3 commits intosaltstack:masterfrom
dwoz merged 3 commits intosaltstack:masterfrom
Conversation
twangboy
previously approved these changes
Apr 4, 2025
Contributor
|
This has some pre-commit and docs failures |
twangboy
approved these changes
Aug 28, 2025
|
Congratulations on your first PR being merged! 🎉 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What does this PR do?
It adds to the GPG documentation so that it's easy for users to import GPG encrypted data within other pillar files.
The context for this was it took me waaaayyyy to long to find this solution to what would seem to be a common problem - especially given the prevalence of salt-stack formulas that rely on pillar data.
My use case was I wanted to define my secrets in one pillar, then have other pillar files use this (ie. database password used by the postgres-formula pillar and also my applications pillar).
What issues does this PR fix or reference?
References #36673 but doesn't directly fix it.
Merge requirements satisfied?
Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.htmlIs this required for documentation updates?Tests written/updatedN/ACommits signed with GPG?
No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.