pulumi/pkg/resource/deploy
Joe Duffy 0290283e6f
Skip unknown properties (#524)
It's legal and possible for undefined properties to show up in
objects, since that's an idiomatic JavaScript way of initializing
missing properties.  Instead of failing for these during deployment,
we should simply skip marshaling them to Terraform and let it do
its thing as usual.  This came up during our customer workload.
2017-11-03 13:40:15 -07:00
..
plan.go Track resources that are pending deletion in checkpoints. 2017-10-18 17:09:00 -07:00
plan_apply.go Encrypt secrets in Pulumi.yaml 2017-10-24 16:48:12 -07:00
plan_test.go Encrypt secrets in Pulumi.yaml 2017-10-24 16:48:12 -07:00
snapshot.go Encrypt secrets in Pulumi.yaml 2017-10-24 16:48:12 -07:00
source.go Add a notion of stable properties 2017-10-04 08:22:21 -04:00
source_eval.go Skip unknown properties (#524) 2017-11-03 13:40:15 -07:00
source_fixed.go Rename pulumi-fabric to pulumi 2017-09-21 19:18:21 -07:00
source_null.go Use Stack over Environment to describe a deployment target 2017-10-16 13:04:20 -07:00
step.go Set old.Delete when previewing a CreateReplace step. 2017-10-19 13:08:17 -07:00
target.go Use Stack over Environment to describe a deployment target 2017-10-16 13:04:20 -07:00