thankful-optician-22583
10/28/2019, 11:47 PMapiVersion: v1
preferences: {}
kind: Config
clusters:
- cluster:
server: ${server}
certificate-authority-data: ${certificate-authority-data}
name: current-cluster
contexts:
- context:
cluster: current-cluster
user: runner-user
name: runner-context
current-context: runner-context
users:
- name: runner-user
user:
token: ${token}
wet-sunset-4939
10/29/2019, 2:35 AMambitious-helmet-24352
10/29/2019, 4:11 PMbetter-rainbow-14549
10/29/2019, 5:18 PMearly-musician-41645
10/29/2019, 6:35 PMconst tentacleVpcId = tentacleConfig.require("vpcId");
console.log("VPC-ID: "+tentacleVpcId);
export const tentacleVpc = awsx.ec2.Vpc.fromExistingIds("tentacle-vpc", {
vpcId: tentacleVpcId,
});
However I get this error:
Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: no matching VPC found
I've checked and rechecked everything (account, credentials, resource ids, config, stack) and still no luck.
I ran a pulumi preview --debug
and I see that there's this output:
Reading AWS VPC: {
Filters: [{
Name: "isDefault",
Values: ["true"]
}]
}
The VPC is not the default one. It's one of many VPCs.
How can I make pulumi get a non-default VPC?rich-lamp-32782
10/30/2019, 12:57 AMbetter-actor-92669
10/30/2019, 9:29 AM<pulumi_gcp.compute.ha_vpn_gateway.HaVpnGateway object at 0x107523430>
in python? I want to assign it to a variable or use it later in a script. Thank you in advance!witty-yacht-82771
10/30/2019, 11:19 AMexport const service = new awsx.ecs.FargateService("click-router", {
assignPublicIp: false,
cluster,
subnets: pubSubnets,
desiredCount: 2,
taskDefinition: taskDef
});
and then in my tests, I’m trying to do:
it("should have 2 desired instances", async () => {
const di = await promise(service.service.desiredCount);
expect(di).to.equal(2);
});
I get the error that the variable di
is undefined. How can I do tests on assigned values prior to deploying?quiet-wolf-18467
10/30/2019, 11:45 AMquiet-wolf-18467
10/30/2019, 11:46 AMpulumi:pulumi:Stack devrel-metrics-production
~ ├─ gcp:container:Cluster metrics update [diff: ~minMasterVersion,nodeVersion]
+- ├─ pulumi:providers:kubernetes metrics replace [diff: ~kubeconfig]
+- ├─ kubernetes:core:Namespace community replace [diff: ~metadata,provider]
+- ├─ kubernetes:core:ServiceAccount community replace [diff: ~metadata,provider]
+- ├─ kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role> community replace [diff: ~metadata,provider]
+- └─ kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> community replace [diff: ~metadata,provider,roleRef,subjects]
quiet-wolf-18467
10/30/2019, 11:48 AMprovider
is passed along to many smaller projects / repositories - is this going to blow them all away? 😞quiet-wolf-18467
10/30/2019, 12:17 PMResources:
~ 1 updated
9 unchanged
quiet-wolf-18467
10/30/2019, 12:17 PMquiet-wolf-18467
10/30/2019, 1:16 PMhelm
CLI. Be sure to install that first! See
instructions below." but I don't can't find anything in the code that would explain why its required
agreeable-australia-82656
10/30/2019, 3:53 PMloud-journalist-52263
10/30/2019, 3:54 PMIngress .status.loadBalancer field was not updated with a hostname/IP address
as described in https://www.pulumi.com/docs/troubleshooting/#ingress-status-loadbalancer
I'm using the Nginx ingress controller and I haven't been able to find any information about what configurations might affect the status.loadBalancer
field. Does anyone have any tips on resolving this with Nginx? If I revert to 1.0, the timeout goes away.important-leather-28796
10/30/2019, 3:58 PMpulumi up
referenced something about deleting the old cluster still in progress. Regardless, old cluster is gone, but my stack thinks not. A pulumi refresh
yields Preview failed: Get <https://34.70.69.68/api?timeout=32s>: dial tcp 34.70.69.68:443: i/o timeout
. I’m just looking to fully destroy, then move forward again - how can I get synced and destroyed when refresh
is failing?ancient-memory-38025
10/30/2019, 4:02 PMStackReference
to refer to the ECS cluster created in project 1 but when I run p up
in project 2 it's generating a a whole new cluster?!ancient-memory-38025
10/30/2019, 4:03 PMconst tvxClusterS = aws.ecs.Cluster.get(`${identifier}-clustera`, stackCluster.getOutput(config.require("clusterName")))
const tvxVpcIdS = awsx.ec2.Vpc.fromExistingIds(`${identifier}-networka`, {
vpcId: stackCluster.getOutput(config.require("vpcId"))
})
// const tvxVpcIdS = aws.ec2.Vpc.get(`${identifier}-networka`, stackCluster.getOutput(config.require("vpcId")))
const tvxCluster = new awsx.ecs.Cluster(`${identifier}-clusterb`, {
cluster: tvxClusterS,
vpc: tvxVpcIdS
})
const ecsService = new awsx.ecs.EC2Service(`${identifier}-svc`, {
cluster: tvxCluster,
taskDefinitionArgs: {
containers: {
app: {
image: awsx.ecs.Image.fromPath(`${identifier}-img`, "./app"),
portMappings: [{
containerPort: 3000,
hostPort: 80,
protocol: "tcp"
}]
}
},
},
desiredCount: 2
})
const app = new Service(`${identifier}-svc-instance`, ecsService)
ancient-memory-38025
10/30/2019, 4:03 PMhallowed-pilot-33885
10/30/2019, 4:53 PMambitious-ram-5811
10/30/2019, 5:57 PMrg
search revealed nadabroad-dog-22463
10/30/2019, 5:58 PMambitious-ram-5811
10/30/2019, 5:58 PMbroad-dog-22463
10/30/2019, 5:59 PMazure.compute.BastionHost
important-leather-28796
10/30/2019, 7:50 PMf1-micro
, specifically invalid machine type fl-micro in zone us-central1-a: googleapi: Error 404: The resource 'projects/acme/zones/us-central1-a/machineTypes/fl-micro' was not found, notFound
, but I can manually create the same thing in the gcp console. What am I missing?broad-dog-22463
10/30/2019, 7:54 PMimportant-leather-28796
10/30/2019, 7:57 PMglamorous-television-20475
10/30/2019, 8:00 PMkustomize build
command to generate the final resource yaml and use that with from pulumi_kubernetes.yaml import ConfigFile
.ambitious-helmet-24352
10/30/2019, 8:22 PMambitious-helmet-24352
10/30/2019, 8:22 PM