sticky-piano-10761
03/25/2019, 3:11 PMbillowy-garage-68819
03/25/2019, 3:22 PMfull-dress-10026
03/25/2019, 4:31 PMfierce-dinner-20116
03/25/2019, 4:58 PMfresh-flag-12765
03/25/2019, 6:12 PMbetter-rainbow-14549
03/25/2019, 6:25 PMModerate Denial of Service
Package js-yaml
Dependency of @pulumi/kubernetes
better-rainbow-14549
03/25/2019, 6:25 PMgray-city-50684
03/25/2019, 6:32 PMpulumi config set cloudflare:email <value>
error: an unhandled error occurred: Program exited with non-zero exit code: 1gray-city-50684
03/25/2019, 6:33 PMbetter-rainbow-14549
03/25/2019, 6:37 PMdnsZone: azure.dns.Zone | (azure.dns.GetZoneResult & azure.dns.GetZoneArgs) | { resourceGroupName: pulumi.Input<string>, name: pulumi.Input<string>, id: pulumi.Input<string> }
important-leather-28796
03/25/2019, 6:41 PMlocations
matching the api https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/projects.locations.clusters#Clusterdamp-book-35965
03/25/2019, 8:03 PMbillions-lock-73409
03/25/2019, 8:43 PMaws.lambda.CallbackFunction
class, and am referencing some parameters needed for launching fargate tasks. However the serialization seems to be properly including the values but they aren’t accessible as written in the ecs.runTask
call. Example function in thread.important-leather-28796
03/25/2019, 9:25 PMup
the fix, and it seems I cannot destroy
either. error: [409] Conflict: Another update is currently in progress
. I also tried refresh but of course it fails due to the original error. What is the proper way to force a destroy?cool-kite-89497
03/25/2019, 9:53 PMearly-musician-41645
03/25/2019, 10:55 PMbrainy-psychiatrist-41826
03/25/2019, 11:56 PMdamp-book-35965
03/26/2019, 12:06 AMconst iamRole = new aws.iam.Role(clusterName + "-server", {
assumeRolePolicy: JSON.stringify({
Version: "2012-10-17",
Statement: [{
Action: "sts:AssumeRole",
Principal: {
"AWS": cluster.instanceRole <- this is type=pulumi.Output<aws.iam.Role>;
},
Effect: "Allow"
}]
})
});
damp-book-35965
03/26/2019, 12:06 AMorange-policeman-59119
03/26/2019, 1:12 AMgcp:project
? It'll be a blocker for being able to use multi-project stacks.brainy-psychiatrist-41826
03/26/2019, 2:07 AMboundless-author-24618
03/26/2019, 9:45 AMbetter-rainbow-14549
03/26/2019, 10:32 AM+ kubernetes:core:Namespace ingress creating Retry #0; creation failed: namespaces "ingress" already exists
+ kubernetes:core:Namespace ingress creating error: Plan apply failed: namespaces "ingress" already exists
+ kubernetes:core:Namespace ingress **creating failed** error: Plan apply failed: namespaces "ingress" already exists
worried-engineer-33884
03/26/2019, 3:47 PMbillowy-garage-68819
03/26/2019, 4:51 PMorange-tailor-85423
03/26/2019, 5:29 PMdamp-book-35965
03/26/2019, 7:11 PMcluster.instanceRole.apply(role => role.arn)
This fails as empty or undefined in case of console.log(role.arn)
It shows me all the aws.iam.Role properties fields but none of them exist other than the role itself which is actually a string. So I'm wondering If it's wrongly characterized and just should be a string ?damp-book-35965
03/26/2019, 7:12 PMclusterInstanceRole.apply(role =>
console.log(role)
);
damp-book-35965
03/26/2019, 7:38 PMfull-dress-10026
03/26/2019, 7:52 PMerror: Plan apply failed: [WARN] A duplicate Security Group rule was found on (sg-002c2846717345a56). This may be
a side effect of a now-fixed Terraform issue causing two security groups with
identical attributes but different source_security_group_ids to overwrite each
other in the state. See <https://github.com/hashicorp/terraform/pull/2376> for more
information and instructions for recovery. Error message: the specified rule "peer: 0.0.0.0/0, TCP, from port: 8880, to port: 8880, ALLOW" already exists
It has something to do with awsx.elasticloadbalancingv2.ApplicationLoadBalancer
, passing in securityGroups
, and changing said security groups.