Is there some known issue with deletion of objects from Pulumi stacks not working when we perform a partial update with

pulumi up --target=xxx

? In one of our stacks, I always get an error similar to

Target 'urn:pulumi:<pulumi-stack-name>::<pulumi-project-name>::gcp:dns/recordSet:RecordSet::cname-dev' could not be found in the stack. Did you forget to escape $ in your shell?

I have been careful to ensure that there's no

$

in the URN name as the error message seems to suggest. The reason I need to perform such partial updates is that one of the objects in this Pulumi stack is a GCP VPC private subnet, whose metadata gets updated on a vanilla

pulumi up

, but then Pulumi can't update this subnet URN since it's already being used by a GKE cluster.

I would like to specify a log group name for this callback function on an API Gateway route, but there doesn't seem to be a property available to do so.

const apiGateway = ( queueIDObject ) => {
    return new awsx.apigateway.API( GATEWAY_NAME, {
        routes: [ {
            path: ROUTE,
            method: 'POST',
            // Note wrapping this as a callback function it can have additional attributes set on the lambda
            eventHandler: new aws.lambda.CallbackFunction("write-event-to-sqs", {
                memorySize: 128,
                callback: async ( event, context ) => {
                    return webhookProcess.fire( event, context, queueIDObject );
                },
            description: "write events to queue and return 200"
            })
        } ]
    } );
};

Any ideas on how I could get

eventHandler

logs written to a named log group?

Hi. I have some questions regarding the tf2pulumi tool. Could you please help me with that? 1. Is Terraform 0.12 still not supported? 2. Does the tool support only 2 "output" languages (TS and Python)? 3. From what folder exactly should I run tf2pulumi? I'd like to convert from

terraform/variants/webapi-dev/webapi-dev.tf

to

pulumi/index.ts

.

├── pulumi
│   ├── Pulumi.yaml
│   ├── index.ts
└── terraform
    ├── README.md
    ├── modules
    │   ├── shared
    │   │   └── <http://main.tf|main.tf>
    │   └── webapi
    │       └── <http://main.tf|main.tf>
    └── variants
        ├── shared
        │   └── <http://shared.tf|shared.tf>
        ├── webapi-dev
        │   └── <http://webapi-dev.tf|webapi-dev.tf>
        └── webapi-prod
            └── <http://webapi-prod.tf|webapi-prod.tf>

Is there a REST API for retrieving data from my Pulumi stacks? I have some secrets/resources stored there that I’d like to access with`curl`

I’ve been able to access stack exports, but can’t figure out how to decrypt secrets from the REST API, since I can’t find documentation for it

Hi, is there a documented process on how to upgrade the provider plugins for a specific stack?

I previously created some secrets using

pulumi config set --secret …

Now I want to remove those so I can run the stack from a different location. Just clearing them out of my local config file didn’t seem to do anything

Hey is anybody having a hard time reading AWS docs in Chrome recently? I can't seem to scroll down or expand the sidebar, and have to hop into Firefox to read them. It just started this week, and I don't believe I added any browser extensions that could have borked anything.

Have any guidelines/suggestions been created for using the S3 state backend WRT organizing projects and stacks? I've read https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/ but it seems to focus only on using Pulumi as the state backend.

Hi, I'm running into an issue when trying to run

pulumi up

I am getting the following error

error: deleting urn:pulumi:production::insig-express::awsx:x:ecs:Cluster$awsx:x:autoscaling:AutoScalingGroup$awsx:x:autoscaling:AutoScalingLaunchConfiguration$aws:ec2/launchConfiguration:LaunchConfiguration::apps-autoscaling-prod: error deleting Autoscaling Launch Configuration (app-autoscaling-prod-9341984): ResourceInUse: Cannot delete launch configuration app-autoscaling-prod-9341984 because it is attached to AutoScalingGroup app-autoscaling-prod-654d7a2-Instances-10K7OFBLTHZ2N

  

status code: 400

I've tried everything on this page https://www.pulumi.com/docs/troubleshooting with no luck. Any advice would be appreciated!

Say I have a stack that depends on the output of another stack. when I update the parent stack and the output changes, what is the “best practice” way to cascade changes down to all dependent stacks? currently it seems i need to go and manually run updates in all dependant stacks. the documentation mentions “cascading updates”, is there some other way of managing this? https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies

Hi, thanks for a quick addition of fargate option for EKS. I'm trying that out with code from the example and i'm getting errors around pod creation. Is it some issue with routing, or something to setup beforehand? Thanks!

kubernetes:extensions:Deployment (kube-system/monitoring-influxdb):
    warning: extensions/v1beta1/Deployment is deprecated by apps/v1/Deployment and not supported by Kubernetes v1.16+ clusters.
    error: 2 errors occurred:
    	* resource kube-system/monitoring-influxdb was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'monitoring-influxdb' timed out waiting to be Ready
    	* Minimum number of Pods to consider the application live was not attained

I'm just bumping the question I asked earlier - does anybody know? 😇

Hey guys. I've deployed an awsx.ec2.VPC and an eks.Cluster successfully, but, when trying to destroy, the process gets stuck deleting a subnet and internet gateway. These resources are defined as follows (straight from the tutorial):

const vpc = new awsx.ec2.Vpc(name, {
   subnets: [{type: 'public'}],
   tags: tags,
});

const cluster = new eks.Cluster(name, {
    vpcId: vpc.id,
    subnetIds: vpc.publicSubnetIds, }

Any idea on why it's not destroying properly? Could this be a bug? It's happened before, and I've had to go and manually destroy some underlying resources (load blancers I think). I do have some Helm charts deployed in the cluster (manged with pulumi as well) that include Load Balancer services, and these seem to be scheduled for destruction after the subnet and ig. Might this be it? any suggestions on how to properly manage dependencies for these charts?

I have a question that's not pulumi-specific, but maybe someone can help me out. in digitalocean i was adding DNS records using the ip address of the nginx ingress controller, by getting the service and looking at its

ipAddress

. but in AWS, the

ipAddress

is actually a hostname, so obviously it can't be used as the value for an A record. what's the way to do the same kind of thing in AWS?

I have one question. This is a pulumi + aws question. Scenario: I have a session with no aws env variables || aws credentials set. However I am running in a pod that has a aws role A and the pod is running in a node with aws role B. Now when I run pulumi preview/up. Will pulumi run using the pod's role or the ec2 node's role?

I’m running some unit testing that requires an export to grab the information and make sure the number of resources add up, but I actually DON’T want to clutter my console output with all that information (which I’m getting because of the export.) Is there a way to silence or mute the exported console data?

i want to make a JS object dynamically (i.e. push certain keys based on if/else blocks), and then render that JS object as yaml. some deeply nested keys may be

pulumi.Output<>

s. how can i do this?

Is it possible to prevent (accidental) uncommitted deploy ? Something in Pulumi teams or crossgaurd would be okay too. I see on the pulumi site that pulumi keeps track of when you run

pulumi up

on uncommitted code

Bumping this, hoping someone can help 🙂

Another Pulumi love moment: resource

aliases

rock!

Is there any sort of feature in Pulumi for resource replacement automation/lifecylce hooks? For example, let's say (in AWS) I have an s3 bucket named

my-special-bucket-abc123

and then pulumi sees the need to destroy and recreate. I have create before destroy set. Then it tries to create

my-special-bucket-xyz321

. Let's say I'm good with that but I need the data moved with the change. I could make an ssm automation document that could take a source bucket as input and a destination bucket as input and copy everything over. Would I be able to trigger the execution of that ssm automation document or any other type of script to handle that phase of the pulumi resource replacement lifecycle? I am not currently working on solving this but I'm just curious.

Hey, anyone is using ALB with EKS? I'm following this tutorial and deployment gets stuck on ingress creation. Looks like ALB is not being created. https://www.pulumi.com/blog/kubernetes-ingress-with-aws-alb-ingress-controller-and-pulumi-crosswalk/

Once I export a variable like : pulumi.export("NodeName", node) . (btw node is of type pulumi.Output I guess). How do I access it and print it ? print(NodeName) doesnt work.

Hi. I am using

awsx.ec2.Vpc.getDefault()

to get the default VPC in my account, is there a way to get the default security group in that VPC?

I’m an absolute newb to both Pulumi and Typescript. I’ve decided to throw myself in at the deep end and choose as a first project beyond the quickstart to create a stack that can create new accounts in our org, something I do regularly. To do so I’m using

aws.organizations.Account

but I’d like to see examples of this in use. Sadly, it’s not one of the modules in the examples Github repo so all I can find is the module reference page (which reads like Greek to non-devs like myself). I just need to see one working example. Anyone here have something like that?

Is there any complex project example? I found it hard to setup project's structure using modules/non modules and envs

Hey guys. I'm trying to deploy some docker images to a few Azure container registries, but it's failing to store the credentials and it produces an 'docker push failed: authentication required' error in some of the images, but not others, and not always the same ones. I'm getting the warning about 'your credentials will be stored unencrypted in .docker/config.json', which is fine, but when I check that file, the failing repositories' credentials are not there, while the ok ones are. Anyone encountered this?

Completely newbie question: does Pulumi have something like Terraform Modules? Some package sharing with a central repo to browse? I want to create a VPC with the relevant enpdoins and all that jazz and I’d rather not do it myself.