Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#pulumi-kubernetes-operator
Title
p
prehistoric-kite-30979
09/29/2021, 3:17 PM
It appears that this line of code doesn’t work as expected
https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/pkg/controller/stack/stack_controller.go#L874
If I run a pulumi stack output I can see my secrets are redacted, but they are still in the clear in the stack status.
s
sparse-park-68967
09/30/2021, 2:16 AM
Hmmm we have a test for this...:
https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/test/stack_controller_test.go#L250
The test runs this program:
https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/test/testdata/empty-stack/index.ts#L9
p
prehistoric-kite-30979
09/30/2021, 8:01 PM
might this differ between s3 vs pulumi backend?
Post