how to find out which key it tries to access?

does anybody know if it is possible to get my current GCP project from ambient provider?

gcp.config.project

I think

ah, nice! thanks

anyone have any idea why an

eks.Cluster

would get stuck on destroy when trying to delete a node security group?

aws:ec2:SecurityGroup                                    cluster-nodeSecurityGroup                  deleting...

looks like it can’t be deleted because it’s associated with an ENI, although I can’t quite tell what that ENI is - EKS master maybe?

actually no, it’s an ENI that was attached to a now-deleted EKS worker

Hey all. I'm new to Pulumi and am working on deploying some tasks to AWS with ECS. When I do

pulumi up

all executes fine, but my LaunchConfiguration and AutoScalingGroup never actually get created in AWS, don't show up in my stack Resources. Everything else so far seems to be working fine. Any ideas on why that would be? Also, any idea if it's possible to add Metadata to LaunchConfiguration resources?

I’m wondering.. why ressources are created with a short random string? is this something we can disable?

@white-balloon-205 would it be possible to craft a dynamic resource provider that decorates an existing provider?

I start from a brand new root account and I want to reference the root account in my pulumi program:

export const rootAccount = new aws.organizations.Account(INFRA_CONFIG.REFERENCE_ACCOUNT_NAME, {
  email: INFRA_CONFIG.ROOT_ACCOUNT_EMAIL,
  iamUserAccessToBilling: 'ALLOW',
  parentId: rootOrgUnit.id
});

is it possible to do that? Pulumi error because this user already exist

anyone know why

vpcCniOptions

on

eks.Cluster

doesn’t seem to be taking effect? With this definition:

new eks.Cluster(
    "cluster",
    {
        name: opts.tagName,
        version: opts.version,
        vpcId: opts.vpcId,
        vpcCniOptions: {
            logLevel: "INFO",
            warmEniTarget: 0
        }
    }
);

the

aws-node

env vars look like:

Environment:
      AWS_VPC_K8S_CNI_LOGLEVEL:  DEBUG
      AWS_VPC_K8S_CNI_LOG_FILE:  stdout
      MY_NODE_NAME:               (v1:spec.nodeName)

Pulumi definitely changed something:

Updating (dev):

     Type                                     Name                        Status      Info
     pulumi:pulumi:Stack                      cluster-infrastructure-dev              
     └─ cluster-infrastructure:eksCluster     cluster                                 
        └─ eks:index:Cluster                  cluster                                 
 ~         └─ pulumi-nodejs:dynamic:Resource  cluster-vpc-cni             updated     [diff: +logLevel]

I’ve tried deleting instances in the nodegroup and letting the ASG replace them, but the env vars are still the same

I have all the modules install still getting this error. Not sure if I am still missing module/code to reference from. I'm testing only to create a single ec2 instance

Second update in a row I get

XXX refers to unknown provider YYY

error with the state remaining inconsistent. That’s a problem

How do you retrieve projectNumber (not projectId) for gcp provider?

found it

it's not on

gcp.projects.getProject

but on

gcp.organizations.getProject

Is there a way to add a certificate to an app service?

We currently use the azure cli to upload a pfx and then bind the certificate by thumbprint to the hostname

that's an extremely provider-specific question?

like, i'm sure pulumi has the APIs to do certificate management for the three major clouds, but you might have to be more specific? (Especially if Azure has several ways to host HTTP applications with different methods of attaching certificates)

So I have the following, we recreate a k8s cluster in a parent stack (because many changes require that). Cluster gets replaced, all is good. However a child stack (a separate pulumi run) that depends on this cluster (and created resources in it) will keep thinking it has many resources deployed in a cluster that's now deleted. This means the provider already fails to connect, breaking the state of the child stack quite severely.

i'm using pulumi to create a DO kubernetes cluster. i then use it as the provider to do other things. but those kubeconfigs expire after a week, and the resource's outputs obviously don't regenerate. what is the recommended way of handling this kind of situation?

Is there a pulumi module for working with Sql Server? I want to

get

an existing database and then manage some users and roles via Pulumi

@bitter-dentist-28132 Have you seen this example? https://github.com/pulumi/examples/tree/master/kubernetes-ts-multicloud

Is there already a Pulumi Typescript component implementation available to set up an S3 static site with a CloudFront CDN in front of it?

@early-intern-90238 what does that have to do with my question? i'm already deploying a cluster.... the problem is the kubeconfig it spits out expires after some time

@bitter-dentist-28132 Let me see what mine does in GCP