sparse-quill-89533
06/20/2019, 4:52 PMboundless-monkey-50243
06/20/2019, 5:42 PMfull-dress-10026
06/20/2019, 6:40 PMcool-egg-852
06/20/2019, 8:15 PMpulumi up
that will perform all deletes before creates? This would be really useful in some scenarios. Our current one is moving from manifests to helm. The resource names are the same, but the URNs are different. Having pulumi delete before create would mean we don’t need to resolve these conflicts manually.tall-librarian-49374
06/20/2019, 8:43 PMpulumi up
becomes very slow sometimes. It shows Previewing update
and nothing else for a couple minutes. That goes on for some time, and then everything seems fast again. Last time Node process was high on CPU, but now everything seems idle. I'm on Windows. Anyone experiencing this?busy-umbrella-36067
06/20/2019, 9:43 PMacoustic-france-62702
06/21/2019, 2:34 PMfull-dress-10026
06/21/2019, 3:50 PMpulumi.awsx.autoscaling.AutoScalingGroup
only support ECS? If so, why? Seems like it could support instances that don't use the ECS AMI.
https://github.com/pulumi/pulumi-awsx/blob/a8dd50c8f5be5137686553cfb4a4d62041481f1b/nodejs/awsx/autoscaling/launchConfiguration.ts#L279-L414swift-painter-31084
06/21/2019, 6:00 PMswift-painter-31084
06/21/2019, 6:00 PMswift-painter-31084
06/21/2019, 7:21 PMbillions-lock-80282
06/21/2019, 7:25 PMcool-egg-852
06/21/2019, 7:31 PMconst awsIamPolicy = new aws.iam.Policy('rsin-provider', {
name: `${config.environment}-rsin-provider`,
description: 'Allow rsin-provider to connect to ElasticSearch',
policy: JSON.stringify(pulumi.interpolate`{
Version: '2012-10-17',
Statement: [
{
Action: ['es:*'],
Effect: 'Allow',
Resource: "${elasticSearchDomain.arn}/*"
},
{
Effect: 'Allow',
Action: ['dynamodb:DescribeTable', 'dynamodb:Query', 'dynamodb:Scan'],
Resource: ${clientsTable.arn}
},
{
Effect: 'Allow',
Action: ['dynamodb:DescribeTable', 'dynamodb:Query', 'dynamodb:Scan'],
Resource: ${auditLogsTable.arn}
},
{
Effect: 'Allow',
Action: ['dynamodb:DescribeTable', 'dynamodb:Query', 'dynamodb:Scan'],
Resource: ${linksTable.arn}
},
{
Effect: 'Allow',
Action: ['dynamodb:DescribeTable', 'dynamodb:Query', 'dynamodb:Scan'],
Resource: ${notificationsTable.arn}
},
{
Effect: 'Allow',
Action: ['dynamodb:DescribeTable', 'dynamodb:Query', 'dynamodb:Scan'],
Resource: ${usersTable.arn}
}
]
}`)
});
swift-painter-31084
06/21/2019, 7:43 PMpulumi config
values into a Cloud Function's handler code without including the pulumi package in it? I was having memory issues when I included it.thankful-lamp-48382
06/21/2019, 8:22 PMglamorous-thailand-23651
06/21/2019, 9:04 PM$ kubectl describe nodes | grep 'KubeletNotReady' | head -n1
Ready False Fri, 21 Jun 2019 13:57:30 -0700 Fri, 21 Jun 2019 13:50:29 -0700 KubeletNotReady runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
to my eye, it seems to be same/similar issue as:
https://github.com/pulumi/pulumi-kubernetes/issues/578
https://github.com/pulumi/pulumi-eks/issues/174
is there a known workaround?nice-airport-15607
06/21/2019, 10:46 PMcreate-data-source
there’s an option for HTTP to have authorizationConfig
option, but i don’t see that in @pulumi/aws/appsync/dataSource.d.ts
. Any ideas how to add authorization to an AppSync HTTP request?average-dream-51210
06/23/2019, 2:11 AMaverage-dream-51210
06/23/2019, 2:11 AMaverage-dream-51210
06/23/2019, 2:12 AMaverage-dream-51210
06/23/2019, 2:48 AMaverage-dream-51210
06/23/2019, 2:48 AMaverage-dream-51210
06/23/2019, 2:48 AMaverage-dream-51210
06/23/2019, 2:48 AMaverage-dream-51210
06/23/2019, 2:49 AMaverage-dream-51210
06/23/2019, 2:50 AMaverage-dream-51210
06/23/2019, 4:49 AMswift-dinner-29731
06/23/2019, 8:40 AMaverage-dream-51210
06/23/2019, 7:46 PMbillions-lock-73409
06/24/2019, 2:56 PM