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

Document how to use GPG encrypted pillar within another pillar file #63504

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

alexhayes
Copy link

@alexhayes alexhayes commented Jan 18, 2023

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?

Commits 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.

@alexhayes alexhayes requested a review from a team as a code owner January 18, 2023 12:26
@alexhayes alexhayes requested review from whytewolf and removed request for a team January 18, 2023 12:26
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.

2 participants