billions-lock-80282
06/24/2019, 3:17 PMbillions-lock-80282
06/24/2019, 3:17 PMindex.ts(9,5): error TS2345: Argument of type '{ agentPoolProfile: { count: number; name: string; osDiskSizeGb: number; osType: string; vmSize: string; }[]; dnsPrefix: string; location: Output<string>; name: string; resourceGroupName: Output<string>; servicePrincipal: { ...; }; tags: { ...; }; }' is not assignable to parameter of type 'KubernetesClusterArgs'.
Object literal may only specify known properties, but 'agentPoolProfile' does not exist in type 'KubernetesClusterArgs'. Did you mean to write 'agentPoolProfiles'?
quaint-queen-45003
06/24/2019, 3:26 PMswift-dinner-29731
06/24/2019, 4:39 PMplain-businessperson-30883
06/24/2019, 5:20 PM$ pulumi --verbose 4 stack rename prod
error: [400] Bad Request: could not deserialized deployment
busy-umbrella-36067
06/24/2019, 6:04 PM@pulumi/eks/Cluster
?
This is what I've got so far, the modifications (AWS_PROFILE
env var) never make it to the provider resource thats created
const modifiedKubeconfig = this.cluster.kubeconfig.apply(kubeconfig => {
kubeconfig.users[0].user.exec.env = [{"AWS_PROFILE": "staging"}]
return kubeconfig
})
this.provider = new kube.Provider("test", { kubeconfig: modifiedKubeconfig.apply(JSON.stringify) }, { parent: this })
glamorous-thailand-23651
06/24/2019, 7:39 PMlemon-spoon-91807
06/24/2019, 8:55 PM@pulumi/awsx
. Our next release has a bunch of fixes in it based on early feedback from the Crosswalk launch. Tried very hard to ensure these fixes wouldn't affect existing stacks, but def let us know if you see otherwise. More information is avialable here: https://pulumi-community.slack.com/archives/CB36DSVSA/p1561409623039300proud-alarm-92546
06/24/2019, 8:56 PMlemon-spoon-91807
06/24/2019, 9:00 PMaverage-dream-51210
06/25/2019, 3:17 AMaverage-dream-51210
06/25/2019, 3:18 AMaverage-dream-51210
06/25/2019, 3:18 AMaverage-dream-51210
06/25/2019, 3:19 AMswift-dinner-29731
06/25/2019, 7:55 AMconst nlb = new awsx.elasticloadbalancingv2.NetworkLoadBalancer("some-nlb", {external: true });
const tg = nlb.createTargetGroup("some-tg", { port: 3000 });
const listener = tg.createListener("some-http-listener", { port: 80 });
const listener2 = tg.createListener('https-listener', {
certificateArn: certificate.arn,
loadBalancerArn: nlb.arn,
port: 443,
protocol: "TLS",
sslPolicy: "ELBSecurityPolicy-2016-08"
});
let service = new awsx.ecs.FargateService("some-app", {
desiredCount: 1,
taskDefinitionArgs: {
containers: {
myapp: {
image: awsx.ecs.Image.fromPath("app", "../"),
memory: 512,
portMappings: [listener],
},
},
},
});
const webDnsRecord = new aws.route53.Record("webDnsRecord", {
name: domain,
type: "A",
zoneId: hostedZoneId,
aliases: [{
evaluateTargetHealth: true,
name: listener.endpoint.hostname,
zoneId: listener.loadBalancer.zoneId, <!!! problem here>
}],
}, { dependsOn: sslCertValidationIssued });
How to get zoneId for elastic load balacer ?
Because in this code I had this error :
error: awsroute53/recordRecord resource 'webDnsRecord' has a problem: "alias.0.zone_id": required field is not setswift-dinner-29731
06/25/2019, 7:56 AMconst balancer = aws.elasticloadbalancing.getLoadBalancer({
name: 'some-nlb',
});
most-judge-33290
06/25/2019, 1:43 PMtg.loadBalancer.loadBalancer.zoneId
cool-egg-852
06/25/2019, 2:05 PMerror: Plan apply failed: deleting urn:pulumi:production::rsin-provider::aws:iam/policy:Policy::rsin-provider: Error deleting IAM policy arn:aws:iam::137361304112:policy/production-rsin-provider: DeleteConflict: Cannot delete a policy attached to entities.
swift-dinner-29731
06/25/2019, 3:34 PMpulumi up index1.js
quaint-zoo-42723
06/25/2019, 4:03 PMswift-dinner-29731
06/25/2019, 4:06 PMswift-dinner-29731
06/25/2019, 4:08 PMproud-alarm-92546
06/25/2019, 4:23 PMswift-dinner-29731
06/25/2019, 4:37 PMtimeout while waiting for state to become 'true' (last state: 'false', timeout: 10m0s)
and after this, i have +1 running task, but not replacing existing
It stucks on the taskDefinition
└─ awsx:x:ecs:FargateService
~ └─ aws:ecs:Service updating [diff: ~taskDefinition]
What can be a problem ?swift-painter-31084
06/25/2019, 4:57 PMThe provided key element does not match the schema
swift-painter-31084
06/25/2019, 4:58 PMendpoint.get( '/posts/{postId}', ( req, res ) => {
const post = req.params.postId;
console.log( post );
postsTable.get( { post } ).then( ( value ) => {
res.status( 200 ).json( value );
} );
} );
worried-engineer-33884
06/25/2019, 7:16 PMcreate
to fail?damp-pillow-67781
06/25/2019, 8:38 PM.json
or a .yaml
file, but when calling object.body()
it shows undefined. I wonder is this the proper way to get the content or any other suggestions on how to get that? The code I have now: const latestFile = aws.s3.getBucketObject({
bucket: bucket,
key: `${key}/pod-settings_latest.json`,
});
console.log(`latest file: ${latestFile.body}`);
which have the output as undefined
.glamorous-printer-66548
06/25/2019, 10:42 PM<http://pulumi.io|pulumi.io>
) and some other stacks in that project use the local
backend? The use case is that some of our engineers want to deploy to their personal minikube in which case it would make more sense to use the local
backend.rich-lamp-32782
06/26/2019, 1:36 AM