white-balloon-205
colossal-beach-47527
08/04/2018, 4:08 PMstocky-spoon-28903
08/04/2018, 4:13 PMstocky-spoon-28903
08/04/2018, 5:25 PMstocky-spoon-28903
08/04/2018, 5:25 PMbig-piano-35669
pulumi stack export
-- and it doesn't contain sensitive info, would you mind sharing and/or filing an issue with it?stocky-spoon-28903
08/04/2018, 5:34 PMbig-piano-35669
stocky-spoon-28903
08/04/2018, 5:35 PMstocky-spoon-28903
08/04/2018, 5:36 PMstocky-spoon-28903
08/04/2018, 5:37 PMinputs. generateJavaKeyStore
was false. However, running pulumi update
didn’t show an update to environment
on the function.big-piano-35669
urn:pulumi:vault-test-dev::pulumi-vault-test::operator-error:aws:LambdaCert::algo-vault-lambda-cert
resource has an empty parent
property. This should never happen except for the top-level stack resource. I vaguely remember some bug a while back where if the resource got created "late" in the asynchronous evaluation of a script, it would get mis-parented, but I thought we fixed this.
I'll file an issue on our side and take a look.stocky-spoon-28903
08/04/2018, 6:26 PMaws.iam.PolicyDocument::merge
would be a useful thing. Basically something that would go through statements in several policy fragments and find the intersection.bland-lamp-97030
08/05/2018, 12:39 AMstocky-spoon-28903
08/05/2018, 10:40 PMpulumi-aws
about cases where objects could be passed instead of IDs in some of the less-used areas of the SDK. I intend to address all of them at some point this week but thought I’d open issues to refer back to as I come across specifics. Please let me know if you’d rather have an omnibus issue for these to reduce noise etcstocky-spoon-28903
08/05/2018, 11:25 PMaws.autoscaling.Group
. The following property value:
tags: [
{
key: "Name",
value: "Vault Server",
propagateAtLaunch: true,
},
],
gives an error when updating:
Previewing update of stack 'vault-test-dev'
Previewing changes:
Type Name Plan Info
* pulumi:pulumi:Stack pulumi-vault-test-vault-test-dev no change 1 error
~ ├─ operator-error:aws:vault:VaultServers algo-vault-servers update changes: + physicalStorageTableName,serverCount,ser
+ │ └─ aws:ec2:PlacementGroup algo-vault-placement-group create
* └─ global global no change 1 error
Diagnostics:
global: global
error: aws:autoscaling/group:Group resource 'algo-vault-autoscaling-group' has a problem: tag.0: expected object, got slice
pulumi:pulumi:Stack: pulumi-vault-test-vault-test-dev
error: One or more resource validation errors occurred; refusing to proceed
error: an error occurred while advancing the preview
stocky-spoon-28903
08/05/2018, 11:27 PMdev
dependency of @pulumi/aws
, so the type definition is:
readonly tags?: pulumi.Input<{
key: pulumi.Input<string>;
propagateAtLaunch: pulumi.Input<boolean>;
value: pulumi.Input<string>;
}[]>;
stocky-spoon-28903
08/05/2018, 11:32 PMstocky-spoon-28903
08/05/2018, 11:34 PMtagsCollection
doesn’t work either (which makes sense given the above):
Diagnostics:
aws:autoscaling:Group: algo-vault-autoscaling-group
error: Plan apply failed: creating urn:pulumi:vault-test-dev::pulumi-vault-test::operator-error:aws:vault:VaultServers$aws:autoscaling/group:Group::algo-vault-autoscaling-group: algo-vault-autoscaling-group-dae2d47: invalid tag attributes: key missing
error: update failed
white-balloon-205
stocky-spoon-28903
08/07/2018, 12:15 AMaws.elasticloadbalancingv2.Listener
is missing a MaxItemsOne: boolRef(true)
on the defaultActions
propertycolossal-beach-47527
08/07/2018, 4:34 AMpulumi preview
ran in your CI/CD system on GitHub. Or optionally requiring another project member to review and approve infrastructure changes to a stack.
If you are interested in providing feedback on the design and/or would like early access to prototypes, please send me a direct message. I’d love to get your input and will follow up with the details for how to get started!stocky-spoon-28903
08/07/2018, 2:52 PM~ ├─ pulumi:providers:aws default update changes: ~ version
and
warning: resource plugin aws is expected to have version >=0.14.6-dev-1533615635-g36bed34, but has 0.14.6-dev-1533603906-g1e50892; the wrong version may be on your path, or this may be a bug in the plugin
stocky-spoon-28903
08/07/2018, 2:52 PMstocky-spoon-28903
08/07/2018, 3:35 PMstocky-spoon-28903
08/07/2018, 6:14 PMmicroscopic-florist-22719
stocky-spoon-28903
08/07/2018, 6:14 PM"traffic"
stocky-spoon-28903
08/07/2018, 6:14 PMnumber | "traffic"
stocky-spoon-28903
08/07/2018, 6:15 PM