salmon-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 PMbroad-dog-22463
07/22/2019, 8:06 PMbroad-dog-22463
07/22/2019, 8:06 PMadamant-dress-73325
07/22/2019, 9:19 PMconst qaVpc = awsx.ec2.Vpc.fromExistingIds("blah-api-docs-qa-vpc", {
vpcId: qaVpcId,
privateSubnetIds: vpcPrivateSubnetIds
});
But this gives me a type error. I have a pulumi.Output<string[]>
but the input args want a pulumi.Input<string>[]
, how can I get the types to line up?stocky-spoon-28903
07/22/2019, 9:21 PMadamant-dress-73325
07/22/2019, 9:22 PMstocky-spoon-28903
07/22/2019, 9:23 PMpulumi.Input<pulumi.Input<string>[]>
therestocky-spoon-28903
07/22/2019, 9:23 PMstocky-spoon-28903
07/22/2019, 9:23 PMadamant-dress-73325
07/22/2019, 9:23 PMmodern-bear-85657
07/22/2019, 10:30 PMincalculable-lock-7238
07/22/2019, 10:45 PMglamorous-waitress-51149
07/23/2019, 8:09 AMbored-river-53178
07/23/2019, 12:40 PMadamant-dress-73325
07/23/2019, 3:40 PMmillions-judge-24978
07/23/2019, 6:30 PMswift-painter-31084
07/23/2019, 8:04 PMdamp-book-35965
07/23/2019, 10:05 PMpulumi preview --config
is missing but pulumi up --config
exists..I'm on pulumi version v0.17.17
Has this been fixed in the more recent versions ? Is this intentional ?bitter-island-28909
07/24/2019, 2:24 PMcool-egg-852
07/24/2019, 4:42 PMearly-musician-41645
07/24/2019, 5:19 PMincalculable-angle-91273
07/24/2019, 5:38 PMloud-nest-15724
07/24/2019, 6:12 PMPreviewing update (testing):
Type Name Plan Info
pulumi:pulumi:Stack aws-js-s3-folder-testing 1 error; 13 messages
Diagnostics:
pulumi:pulumi:Stack (aws-js-s3-folder-testing):
error: Unrecognized flag --query-mode
usage: RUN <flags> [program] <[arg]...>
where [flags] may include
--project=p set the project name to p
--stack=s set the stack name to s
--config.k=v... set runtime config key k to value v
--parallel=p run up to p resource operations in parallel (default is serial)
--dry-run true to simulate resource changes, but without making them
--pwd=pwd change the working directory before running the program
--monitor=addr [required] the RPC address for a resource monitor to connect to
--engine=addr the RPC address for a resource engine to connect to
--tracing=url a Zipkin-compatible endpoint to send tracing data to
and [program] is a JavaScript program to run in Node.js, and [arg]... optional args to it.
error: an unhandled error occurred: Program exited with non-zero exit code: 255
the version of the pulumi cli is v0.17.25
and the node version is v10.16.0nice-airport-15607
07/24/2019, 6:48 PMmodern-bear-85657
07/24/2019, 7:12 PMconst ami = await getAmi({
mostRecent: true,
nameRegex: `amzn2-ami-hvm-.*-x86_64-ebs`,
owners: ['amazon']
})
modern-bear-85657
07/24/2019, 7:12 PMconst ami = await getAmi({
mostRecent: true,
nameRegex: `amzn2-ami-hvm-.*-x86_64-ebs`,
owners: ['amazon']
})
salmon-account-74572
07/24/2019, 7:13 PM--filters
command line option). Maybe there's something similar for this function?