fierce-dinner-20116
07/18/2019, 10:16 PMpost-step event returned an error: failed to verify snapshot: resource urn:pulumi:ds-dog-k8s-dev::sg-deploy-k8s-helper::kubernetes:core/v1:Secret::langserver-auth refers to unknown provider urn:pulumi:ds-dog-k8s-dev::sg-deploy-k8s-helper::pulumi:providers:kubernetes::dogfood-full-k8s::3a90eb1d-d8d5-4272-ae29-300c34caaab9
cool-egg-852
07/18/2019, 11:42 PMfew-processor-86645
07/19/2019, 8:59 AMlimited-rainbow-51650
07/19/2019, 10:21 AMresource "aws_iam_user_login_profile" "ringo" {
user = aws_iam_user.ringo.name
pgp_key = "keybase:ringods"
}
to Pulumi TS code
const iam_user_login_profile_ringo = new aws.iam.UserLoginProfile("ringo",
{
user: iam_user_ringo.name,
pgpKey: "keybase:ringods"
},
{
import: "ringo"
})
But on preview
, I get this warning:
...
= └─ aws:iam:UserLoginProfile ringo import [diff: +pgpKey]; 1 warning
Diagnostics:
aws:iam:UserLoginProfile (ringo):
warning: inputs to import do not match the existing resource; importing this resource will fail
The PGP key indicator is the same string. How come a difference is detected?crooked-jordan-34725
07/19/2019, 11:30 AMcrooked-jordan-34725
07/19/2019, 11:30 AMcrooked-jordan-34725
07/19/2019, 11:30 AMlimited-rainbow-51650
07/19/2019, 2:07 PMOutput<string>
. The value in it is the string version of a number. How can I get the number value as an input for another resource?fresh-flag-12765
07/19/2019, 5:22 PMfresh-flag-12765
07/19/2019, 5:23 PMdial tcp: lookup <http://xxx.gr7.us-east-1.eks.amazonaws.com|xxx.gr7.us-east-1.eks.amazonaws.com>: no such host
fresh-flag-12765
07/19/2019, 5:36 PMmillions-judge-24978
07/19/2019, 6:47 PMdiff
details shows nothing being done.clever-nest-47198
07/19/2019, 7:21 PMmodern-bear-85657
07/19/2019, 8:09 PMArgument of type '{ name: Output<string>; }' is not assignable to parameter of type 'GetSecurityGroupArgs'.
early-musician-41645
07/19/2019, 11:07 PMearly-musician-41645
07/19/2019, 11:07 PMSecretVersion
aren't totally clear how to use itcuddly-eye-68174
07/20/2019, 10:31 AMearly-intern-90238
07/21/2019, 4:04 PMearly-intern-90238
07/21/2019, 4:04 PMearly-intern-90238
07/21/2019, 4:05 PMbored-river-53178
07/22/2019, 1:01 AMbest-xylophone-83824
07/22/2019, 11:17 AMbest-xylophone-83824
07/22/2019, 11:31 AMbest-xylophone-83824
07/22/2019, 11:38 AMsalmon-beard-79336
07/22/2019, 11:39 AMdiff
and check
in a custom Resource?important-leather-28796
07/22/2019, 4:04 PMpreview
and while we have not made changes, we just had a change pop up as part of our infrastructure
stack that looks pretty ominous. Am I correct in thinking this is going to update the cluster and delete/recreate all that is listed here as replace
? This seems like it would be a very bad/production downtime event…wouldn’t it?incalculable-lock-7238
07/22/2019, 4:11 PMvictorious-ambulance-28127
07/22/2019, 5:42 PMglamorous-printer-66548
07/22/2019, 8:04 PM{
"urn": "urn:pulumi:my-stack::my-stack::pulumi:providers:kubernetes::my-cluster",
...
"inputs": {
"kubeconfig": "...",
"namespace": "my-namespace"
}
...
}
and after the upgrade pulumi wants to converge to this state:
{
"urn": "urn:pulumi:my-stack::my-stack::pulumi:providers:kubernetes::my-cluster",
...
"inputs": {
"kubeconfig": "...",
"namespace": "my-namespace"
},
"outputs": {
"kubeconfig": "...",
"namespace": "my-namespace"
}
...
},
As you can see after the upgrade suddenly an "outputs" section that wasn't there before is being added. Because it didn't exist before pulumi attempts to do a replacement.
I can workaround the issue by copying the "inputs" and pasting them as "outputs" and importing the fixed state.json which I did for a few stacks but since we have almost 100 stacks this is not a scalable solution.
Is this a known issue and is there a better solution to the problem?
I can btw reproduce this problem quite consistently (my machine, other machines, CI).broad-dog-22463
07/22/2019, 8:06 PM