Does kubernetes provider support server side apply?

Hi, I am trying to change the config map belonging to the ingress in minikube. I have tried import and it just creates a new one. I’ve also tried using get to get it and modify the data but it doesn’t seem to change it. How should this be done?

has anyone got any pointers on installing Helm charts into non-default/current namespaces? I’ve tried passing a custom provider to Helm as mentioned here, but it gets ignored https://github.com/pulumi/pulumi-kubernetes/issues/217#issuecomment-504160101

is there any way to manage aws codecommit specific credentials in pulumi? https or ssh codecommit credentials

i'm using pulumi in CI, in a pipeline where i have nightly, staging, and prod jobs. the staging job triggers after nightly finishes, and i'd expected that once a

pulumi up

has finished, it unlocks the stack. this doesn't seem to be the case; the staging job gets a 409 error. is this a bug, or a known problem with app.pulumi.com's concurrency management?

Hi, we are taking advantage of the import flag with our aws resources, is there a way to have the diff that is part of the output -> go into something that can be easily serialized as a resource object

Hi, hopefully this is a simple one, how do I access the parameters which the provider libraries require. Specifically I want to get the value of the current region this doesn't seem to get me what I want

const region: string = new pulumi.Config().require("aws:region");

pulumi stack rename

resulted in error: error: rename .pulumi/history/dev-bfstack-emesa1 .pulumi/history/dev-bfstack-emesa: no such file or directory the state is was in s3 now I can access the stack at all,

pulumi up

gives the error 'error: failed to load checkpoint: blob (code=NotFound): NoSuchKey: The specified key does not exist. status code: 404, request id: 52CA127D3A77A221, host id: +t5rZUXVdawXQCrYFQrMX4KWh3Us/vWLu9ltJ7Hj01aHn2Irz8c2QCkztOqEyHlhVhHrBTvNT+0='

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?