best-hydrogen-40271
10/22/2019, 10:22 PMbest-hydrogen-40271
10/22/2019, 10:22 PMbest-hydrogen-40271
10/22/2019, 10:22 PMbest-hydrogen-40271
10/22/2019, 10:23 PMbest-hydrogen-40271
10/22/2019, 10:24 PMbest-hydrogen-40271
10/22/2019, 10:25 PMbest-hydrogen-40271
10/22/2019, 10:25 PM+- │ ├─ gcp:container:Cluster primary replace [diff: +nodeConfig]
best-hydrogen-40271
10/22/2019, 10:38 PMbest-hydrogen-40271
10/22/2019, 10:39 PMbest-hydrogen-40271
10/22/2019, 10:43 PMbest-hydrogen-40271
10/22/2019, 10:44 PMcrooked-jelly-50877
10/22/2019, 10:49 PMcrooked-jelly-50877
10/22/2019, 10:49 PMcrooked-jelly-50877
10/22/2019, 10:50 PMreplicaCount
is getting set to a float 1.0
- not an integercrooked-jelly-50877
10/22/2019, 10:50 PMcrooked-jelly-50877
10/22/2019, 10:50 PMcrooked-jelly-50877
10/22/2019, 10:51 PMError: render error in "nginx-ingress/templates/default-backend-poddisruptionbudget.yaml": template: nginx-ingress/templates/default-backend-poddisruptionbudget.yaml:1:7: executing "nginx-ingress/templates/default-backend-poddisruptionbudget.yaml" at <gt .Values.defaultBackend.replicaCount 1.0>: error calling gt: incompatible types for comparison
Error: Error: Command failed: helm template /var/folders/br/vk7vq4s17z50g66njs1gmlc80000gn/T/tmp-78327rwjsRXZ39Xkh/nginx-ingress --name nginx-ingress --values /var/folders/br/vk7vq4s17z50g66njs1gmlc80000gn/T/tmp-78327rwjsRXZ39Xkh/nginx-ingress/values.yaml --values /var/folders/br/vk7vq4s17z50g66njs1gmlc80000gn/T/tmp-783273FSDGnkfbySQ.yaml --namespace nginx
Error: render error in "nginx-ingress/templates/default-backend-poddisruptionbudget.yaml": template: nginx-ingress/templates/default-backend-poddisruptionbudget.yaml:1:7: executing "nginx-ingress/templates/default-backend-poddisruptionbudget.yaml" at <gt .Values.defaultBackend.replicaCount 1.0>: error calling gt: incompatible types for comparison
at /Users/warren.strange/tmp/forgeops/cluster/pulumi/node_modules/@pulumi/kubernetes/helm/v2/helm.js:112:23
at OutputImpl.<anonymous> (/Users/warren.strange/tmp/forgeops/cluster/pulumi/node_modules/@pulumi/pulumi/output.js:110:47)
at Generator.next (<anonymous>)
at fulfilled (/Users/warren.strange/tmp/forgeops/cluster/pulumi/node_modules/@pulumi/pulumi/output.js:18:58)
crooked-jelly-50877
10/22/2019, 10:51 PMcrooked-jelly-50877
10/22/2019, 10:52 PMdefaultBackend: {
enabled: "false",
replicaCount: 1, // to make helm happy
minAvailable: 1
}
crooked-jelly-50877
10/22/2019, 10:53 PMhelm template
without getting rendering errorscrooked-jelly-50877
10/22/2019, 11:02 PMmillions-judge-24978
10/23/2019, 12:32 AMbillions-lock-73409
10/23/2019, 1:55 PMfuture-morning-96441
10/23/2019, 2:12 PMpulumi up
)?
The Stack's number of resources grew over time and so did the time needed for a deployment (also for updates in a single lambda). I'm thinking of many different approaches of how to speed up thinks, but it would be great to be able to prioritize tasks based on the expected speedup.
Metrics I would be interested in could include:
- time needed to run diff before update
- time needed to upload a lambda
- time needed for requests to Pulumi backend
- maybe also overall and split into resource-types
We are already thinking about splitting the application into several stacks. But still, I'd like to perform an informed choice of where and how to start optimizing our deployment times.
PS: last deployment took about 36 minutes:
- 36 updated ressources
- 476 unchanged resource
Kind regards, Chrisstocky-nail-30268
10/23/2019, 3:06 PMawsx.ec2.Vpc.fromExistingIds
and the ComponentResourceOptions
doesn't have an async
property on it, so I assume at some point getVpc
is being called, and we have no way of making that async. Is there a different way of making this call for it to work?
warning: Synchronous call made to "aws:ec2/getVpc:getVpc" with an unregistered provider.
For more details see: <https://www.pulumi.com/docs/troubleshooting/#synchronous-call>
quiet-wolf-18467
brave-angle-33257
10/23/2019, 6:50 PMerror: Running program '/data/pulumi/infra/aws/company/company-step-functions' failed with an unhandled exception:
TSError: ⨯ Unable to compile TypeScript:
index.ts(53,5): error TS2322: Type 'Output<string>' is not assignable to type 'Input<Topic>'.
code is:
const success_topic_subscription_name = `${company}-collector-${env}-success-email`
const success_topic_subscription = new aws.sns.TopicSubscription(success_topic_subscription_name, {
endpoint: "<https://global.sns-api.chatbot.amazonaws.com>",
protocol: "HTTPS",
topic: success_topic.arn,
});
best-hydrogen-40271
10/23/2019, 7:33 PMprotect
-- will it allow me to tear down everything except `protect`ed resources?best-hydrogen-40271
10/23/2019, 7:33 PMbest-hydrogen-40271
10/23/2019, 7:34 PM