Skip to content

Add note in documentation that special characters may need to be escaped when using pulumi config set --secret #13564

@ahanoff

Description

@ahanoff

I had password with special characters: 9#^XeshqnX$bG9vFPa@r7Ti98uo@sS, which I stored as pulumi config secret and then retrived it from config and stored as AWS SSM secret.
After comparison AWS SSM Secret value and original password don't match

Expected behavior

It should match of course

Current behavior

It doesn't match

Steps to reproduce

  1. Add pulumi secret with special characters (for example 9#^XeshqnX$bG9vFPa@r7Ti98uo@sS )
  2. Take that secret from config and stores it in AWS SecretsManager
  3. Retrieve AWS SecretsManager secret value and compare with original

Context (Environment)

Affected feature

Metadata

Metadata

Assignees

Labels

area/docsImprovements or additions to documentationkind/documentationImprovements or additions to documentationresolution/fixedThis issue was fixed

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions