It looks like

c5.large

is not being allowed as an EC2 instance type

I don't see it down among this list: https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/ec2/#C3Instance2XLarge

Hi, I think it's maybe more like a typescript question then pulumi, but what is the recommended way to structure the infrastructure code? I'm thinking in a similar structure like the attached, the main pont to share "node_modules" and custom "modules" directories, those doesn't have env specific code and use separate directories for the env codes. Would be the best if I could tie the envs to stacks somehow and run pulumi commands from the env directories or maybe run from the root with an index.ts file, which get the stack name programatically and import the code from the correct env. Is there other recommended way to do this?

hmm

if I want to export something that relies on the default network, which requires

await

, how would I go about doing that?

@white-balloon-205 or someone from Pulumi - can you talk about GitHub Actions? Looks really interesting. Can I build a CI/CD pipeline using pulumi & GH?

Are those available to subscribers?

GitHub Actions look really nice. Hopefully they will add me to the beta soon. 🙂

Ran into this issue while trying to setup CI.

☝️ What could be the issue?

I'm trying out some typescript for creating an EKS cluster using the

@pulumi/aws/eks

. I can't figure out what the

vpcConfig

should look like and keep getting this erorr:

let cluster = new aws.eks.Cluster(environment+"-eks-cluster", {
    roleArn     : clusterRole.arn,
    vpcConfig   : {
        vpcId             : config.require("vpc-id"),
        subnetIds         : vpcSubnetIds,
        securityGroupIds  : [clusterSecurityGroup.id],
    },
});

aws:eks:Cluster (online-sandbox-pulumi-poc-eks-cluster):
    error: aws:eks/cluster:Cluster resource 'online-sandbox-pulumi-poc-eks-cluster' has a problem: "vpc_config.0.vpc_id": this field cannot be set

What am I doing wrong?

I thought

vpcId

is a required field, and in fact I'd prefer that the cluster is created in a specific VPC that I choose

I'm not sure about that specific error (@microscopic-florist-22719, any idea?). Note that we have a component that makes creating EKS clusters much easier; see https://github.com/pulumi/examples/blob/96a59f4256412988e9d5d0f744905fe0b1a3b202/aws-ts-eks/index.ts#L8.

So I'm finding myself wedged with the Azure API, particularly with regards to app services.

Not sure if this is the right channel but I am getting a 404 when trying to visit the pulumi dashboard

how hard would it be to get pulumi to output plain text diff files for previews?

not sure if this is pulumi or Azure, but when trying to update a property on trying to update a property of Role Definition, I get an error saying I can't update it in place

ran into another one where I create User Identies, then try to use them, and it says "principalId doesn't exist", which the identity.principalId should be a promise on its own, but I also added a

dependsOn: uai

and same situation

Hi all, has anybody used pulumi to create kubernetes clusters for anything beyond POC (production ?) ?

@stocky-spoon-28903 Does nomad have a similiar interface like kubernetes' Virtual-Kublete? https://github.com/virtual-kubelet

I created a stack at work, where I'm using linux and now I'm tried to update that stack at home, where I'm using windows, pulumi tries to replace all the resource, because it thinks they changed, but checking the diff, the only difference is the line endings. The state stored in pulumi cloud, not locally. My git config has "core.autocrlf=true" setting, but I assume it shouldn't be a problem, because the strings in the state file are generated by pulumi. I'm using pulumi version 0.16.1 on both machines with typescript. What should I set to get a correct state between different platforms?

I’m a ts newbie. Getting a stack trace when running pulumi up

this is on mac os, pulumi 0.16.1

@crooked-jelly-50877 do you have the code that you are trying to pulumi up?

yep - just the sample

gcp-ts-gke

I basically git cloned that sample, set my config, and did a

pulumi up

For anyone else who sees error like this - see reply in the thread above. Node 11 is not currently supported with Pulumi, but we are working on support now for the next release. https://pulumi-community.slack.com/archives/C84L4E3N1/p1540752137087100?thread_ts=1540751756.083600&channel=C84L4E3N1&message_ts=1540752137.087100