flat-river-10700
02/05/2019, 5:46 PMbillions-lock-73409
02/05/2019, 9:01 PMbitter-island-28909
02/05/2019, 9:13 PMaws.s3.BucketObject
- Pulumi reports that an object has been created, and it is present in the state and website UI, but not actually present in AWS. Doing a pulumi refresh
causes the object’s non-existent status to be correctly reflected in the state, and then another pulumi up
creates it correctly.
I’d give you a better repro case if I could, but it’s not happening consistently, so hard to pin down.billions-lock-73409
02/06/2019, 1:22 AMorange-tailor-85423
02/06/2019, 1:49 AMorange-tailor-85423
02/06/2019, 1:49 AMorange-tailor-85423
02/06/2019, 1:50 AMorange-tailor-85423
02/06/2019, 1:50 AMorange-tailor-85423
02/06/2019, 1:50 AMorange-tailor-85423
02/06/2019, 2:05 AMswift-accountant-28554
02/06/2019, 4:31 PMadamant-restaurant-73893
02/06/2019, 4:43 PMadamant-restaurant-73893
02/06/2019, 6:58 PMbusy-umbrella-36067
02/06/2019, 7:34 PMcreate-replace
for all of my k8s resources and the only diff is adding the default namespace
--kubernetes:core/v1:Service: (delete-replaced)
[id=default/external-digibyte-61651]
[urn=urn:pulumi:cointainers-staging::cointainers::standard:Deploy$kubernetes:apps/v1:StatefulSet$kubernetes:core/v1:Service::external-digibyte-61651]
+-kubernetes:core/v1:Service: (replace)
[id=default/external-digibyte-61651]
[urn=urn:pulumi:cointainers-staging::cointainers::standard:Deploy$kubernetes:apps/v1:StatefulSet$kubernetes:core/v1:Service::external-digibyte-61651]
~ metadata : {
+ namespace : "default"
}
helpful-forest-30196
02/06/2019, 8:13 PMbusy-umbrella-36067
02/06/2019, 9:05 PMDiagnostics:
kubernetes:apps:StatefulSet (litecoin-0163):
error: Preview failed: 2 errors occurred:
* Resource 'litecoin-0163' was created but failed to initialize
* Failed to observe the expected number of ready replicas
busy-umbrella-36067
02/06/2019, 10:06 PMread
actions on recoded resources, any idea what those are?best-tent-29186
02/06/2019, 10:11 PMHelm
chart into pulumi. We use the aws-alb-ingress-controller
which means we have the following line in our ingress.
paths:
- path: /*
backend:
serviceName: ssl-redirect
servicePort: use-annotation
This sets up automatic ssl forward at ALB level in AWS.
However Pulumi doesn’t understand this third party rule and is not fully deploying showing:
kubernetes:extensions:Ingress core-django creating... No matching service found for ingress rule: "***-staging.***.com/*" -> "ssl-redirect"
miniature-potato-84713
02/06/2019, 10:22 PMk8s.core.v1.Service()
) and wondering if there’s a problem linked to the isMinikube
setting.helpful-forest-30196
02/06/2019, 10:41 PMorange-tailor-85423
02/07/2019, 12:36 AMpulumi preview
fails due to missing plugin. You then run pulumi plugin install
and it doesn't resolve any?orange-tailor-85423
02/07/2019, 12:39 AMchilly-photographer-60932
02/07/2019, 1:10 AMgcp:dns:RecordSet (frontend):
error: unexpected null property rrdatas[0]
bitter-island-28909
02/07/2019, 3:17 PMaws.ec2.getInstance
(and indeed all the get*
functions) could take Inputs as well as literal values. I can work around it by calling it inside an apply
, but it seems like it would be pretty straightforward to do that by default and keep client code cleaner.early-musician-41645
02/07/2019, 8:16 PMstrong-room-91176
02/07/2019, 8:37 PMhelpful-ice-5738
02/07/2019, 10:37 PMbrainy-magician-83981
02/08/2019, 1:05 AMbillions-lock-73409
02/08/2019, 3:13 PMbillions-lock-73409
02/08/2019, 3:13 PM