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.

Sign up for GitHub

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

Fix heading attribute #12490

Merged
merged 1 commit into from
Aug 9, 2024
Merged

Fix heading attribute #12490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/docs/concepts/secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -590,7 +590,7 @@ The [supported secrets providers](/docs/cli/commands/pulumi_stack_init/) are:
After the provider has been changed, you should be able to run `pulumi preview` and see no proposed changes. Your configuration secrets
and state files are now encrypted using the new secrets provider.

## Committing configuration to source control {# search.keywords="checking version control"}
## Committing configuration to source control { search.keywords="checking version control"}

When you run `pulumi config set --secret` to generate a new Pulumi secret, the Pulumi CLI uses the stack's unique encryption key to encrypt the raw value and store the resulting ciphertext in the stack configuration file (`Pulumi.dev.yaml`, for example). If you opened this file in a text editor, you'd see that the contents would look something like this:

Expand Down
Loading