quiet-wolf-18467
10/25/2019, 11:31 AMquiet-wolf-18467
10/25/2019, 11:31 AMquiet-wolf-18467
10/25/2019, 1:58 PMconst kubernetesProvider = new k8s.Provider("metrics", {
kubeconfig: config.requireSecret("kubeconfig")
});
quiet-wolf-18467
10/25/2019, 2:12 PMpulumi config get kubeconfig > kubeconfig
and loaded this file during pulumi up
. Please tell me there's a better way 🙂quiet-wolf-18467
10/25/2019, 2:28 PMconst kconfig = fs.readFileSync("../kubeconfig").toString();
const kubernetesProvider = new k8s.Provider("metrics", {
kubeconfig: kconfig
});
Fails: error: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provide
But kubectl get pods -n community --kubeconfig=./kubeconfig
works 😞incalculable-diamond-5088
10/25/2019, 3:14 PMtranscriptionJobs.bucket.onObjectCreated('publish', async ev => {
const s3Client = new aws.sdk.S3()
const kinesisCliet = new aws.sdk.Kinesis()
for (const { s3: { bucket, object } } of ev.Records || []) {
console.log({ bucket, object })
}
})
and getting an error:
Error: failed to register new resource publish [aws:lambda/function:Function]: 2 UNKNOWN: failed to compute asset hash: asset path 'node_modules/@lemonade/infra-common' is a directory; try using an archive
quiet-wolf-18467
10/25/2019, 3:36 PMquick-action-34599
10/25/2019, 3:50 PMcreateAutoScalingGroup
on an awsx.ecs.Cluster
. I get the error Property AvailabilityZones cannot be empty
. I don’t see an option for setting availabilityZones
through createAutoScalingGroup
.adamant-dress-73325
10/25/2019, 4:18 PMpulumi config set --secret ...
bored-cartoon-33302
10/25/2019, 4:28 PMcool-egg-852
10/25/2019, 5:20 PMquick-action-34599
10/25/2019, 5:25 PMaws ecs update-service
? The image is being built by CI not using pulumiearly-intern-90238
10/25/2019, 7:01 PMhigh-morning-18773
10/25/2019, 10:35 PMbored-cartoon-33302
10/26/2019, 12:38 PMearly-intern-90238
10/26/2019, 2:35 PMearly-intern-90238
10/26/2019, 8:34 PMearly-intern-90238
10/26/2019, 10:01 PMearly-intern-90238
10/26/2019, 10:11 PMwet-sunset-4939
10/28/2019, 11:23 AMwonderful-daybreak-2504
10/28/2019, 12:17 PMtransformations
? it's a blocker for using helm charts currently...rhythmic-finland-36256
10/28/2019, 5:10 PMpulumi.kubernetes.ConfigFile
and disabling kubectl validation for CRD unknown fields (relating to cert-manager
)rhythmic-finland-36256
10/28/2019, 5:40 PMk8s
resource I can use to create an object of a CRD without implementing a full pulumi custom resource
? Looking into specifying some cert-manager
`Issuer`s and `Certificate`s in code without just dropping everything in a yaml file and using ConfigFile
for it.witty-yacht-82771
10/28/2019, 5:43 PMindex.ts
available for testing? I’m currently exporting them as needed and importing in my tests, but obviously that really clutters up each stack’s output variables.thankful-optician-22583
10/28/2019, 6:33 PMthankful-optician-22583
10/28/2019, 6:34 PMthankful-optician-22583
10/28/2019, 7:40 PMbusy-umbrella-36067
10/28/2019, 8:23 PMpanic: fatal: An assertion has failed: Two resources ('urn:pulumi:fuckit::XXXXX::kubernetes:apps/v1:Deployment::squid' and 'urn:pulumi:fuckit::XXXXX::kubernetes:core/v1:Service::squid') aliased to the same: 'urn:pulumi:fuckit::XXXXX::kubernetes:apps/v1:Deployment::squid'
elegant-crayon-4967
10/28/2019, 9:35 PMearly-musician-41645
10/28/2019, 11:42 PMawsx.ec2.Vpc.fromExistingIds
and it works as expected in a different project.
Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: no matching VPC found
Is there a flag or something I'm missing? The VPC id definitely exists.early-musician-41645
10/28/2019, 11:42 PMawsx.ec2.Vpc.fromExistingIds
and it works as expected in a different project.
Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: no matching VPC found
Is there a flag or something I'm missing? The VPC id definitely exists.white-balloon-205
10/28/2019, 11:45 PMearly-musician-41645
10/28/2019, 11:46 PMsts get-caller-identity
it is set up properly.white-balloon-205
10/28/2019, 11:50 PMaws.getCallerIdentity().then(console.log)
early-musician-41645
10/28/2019, 11:52 PMconst vpcId = tentacleConfig.require("vpcId");
console.log("vpcId: "+vpcId);
export const vpc = awsx.ec2.Vpc.fromExistingIds("tentacle-vpc", {
vpcId: vpcId,
});
white-balloon-205
10/28/2019, 11:55 PMTF_LOG=TRACE pulumi up --debug
(and may need to pipe that output to a file as it will be quite verbose). You can then see the exact calls being made to AWS.early-musician-41645
10/28/2019, 11:57 PMDescribeVpcsResponse
and it has the exact same vpcId
that I'm using in the config... 😕vpcSet
, but later calls with it filled in