busy-soccer-65968
06/04/2020, 10:12 PM"[secret]"
and is there a way to disable it on fields? it's causing massive diffs. I'll thread an example.spec : {
~ template: {
~ spec : {
- containers: "[secret]" <----- HERE
+ containers: [
+ [0]: {
+ command : [
+ [0]: "xxx"
+ [1]: "xxx"
+ [2]: "xxx"
+ [3]: "xxx"
+ [4]: "xxx"
]
+ env : [
+ [0]: {
+ name : "ENVIRONMENT"
+ value: "stage"
}
]
+ image : "<http://0000000000.dkr.ecr.us-west-1.amazonaws.com/test:latest|0000000000.dkr.ecr.us-west-1.amazonaws.com/test:latest>"
+ imagePullPolicy: "Always"
+ name : "test"
+ ports : [
+ [0]: {
+ containerPort: 8000
}
]
+ resources : {
+ limits : {
+ cpu : "4"
+ memory: "8G"
}
+ requests: {
+ cpu : "2"
+ memory: "4G"
}
}
+ volumeMounts : [
+ [0]: {
+ mountPath: "/config"
+ name : "config"
+ readOnly : true
}
]
}
]
- volumes : "[secret]" <----- HERE
+ volumes : [
+ [0]: {
+ name : "config"
+ secret: {
+ secretName: "config"
}
}
]
}
}
}
green-school-95910
06/04/2020, 10:16 PMgetSecret
, requireSecret
or any of their variants
• A value explicitly marked as secret using pulumi.secret(value)
Output
created using any secret is also a secretbusy-soccer-65968
06/04/2020, 10:18 PMcore.v1.Secret
attached to a deploymentgreen-school-95910
06/04/2020, 10:19 PMpulumi.Output
that is set as a secret, probably because it is a sensitive value or used a sensitive value to be generatedbusy-soccer-65968
06/04/2020, 10:20 PMgreen-school-95910
06/04/2020, 10:21 PMbusy-soccer-65968
06/04/2020, 10:21 PMlemon-agent-27707
06/04/2020, 10:22 PMbusy-soccer-65968
06/04/2020, 10:22 PMSecret.ts
I don't see anything obvious to melemon-agent-27707
06/04/2020, 10:23 PMbusy-soccer-65968
06/04/2020, 10:24 PM