everytime i run pulumi up, it does it's thing but complains about not being able to delete a certain resource that i deleted manually

should i just recreate the project ?

I want to check my understanding quickly. I want to register an EC2 instance that I am launching using Pulumi with my SaltStack master server to provision a minion key, and populate it on the instance that I am launching using cloud-init. From what I've been able to gather, this would be a use case for a dynamic provisioner. Is there a different approach that I should be considering?

quick question about pulumi + kustomize i'm generating some passwords via

pulumi/random

i then use

apply

to write the passwords into a local file (within the kustomize folder). this generates another output (let's call it

fileOutput

) then i need to register the kustomize

Directory

... and this is where it gets tricky my first thought was that i should use the

pulumi.DependsOn

option. however DependsOn only accepts resources, and won't accept

fileOutput

any tips?

sorry guys how do i fetch the string from a stringOutput type in go

I get that its' supposed to work as a type of promise, I just need the string ...

it's in go ...

sorry found an example I hope.

Is there any documentation in regards to creating and utilizing your own templates which are not on github.com?

I saw mentions of "dynamic provisioner", but I'm failing to find any description what it is - any links please?

@incalculable-dream-27508 https://www.pulumi.com/docs/intro/concepts/programming-model/#dynamicproviders

thank you

Ah, dynamic provider, not provisioner

I also found this blog on Providers which had a section on provisioners https://www.pulumi.com/blog/dynamic-providers/

does pulumi have a “global” or “project” level config — where you could set config values that are available to all stacks in the project?

hey, is there API for aws event bridge (go) ?

can't seem to find it

How do I get a StackReference to a stack which has an S3 backend? In particular, what is the first part of the "<organization>/<project>/<stack>" StackReference name? I want to load something from another stack in the current project, which I think should be possible, since there's only one backend URL. I've been told that the only reason StackReferences don't work on S3 is because I'm using different URLs for every backend. So that doesn't apply in this case.

Related: having created my state in S3, the stack is written using whichever AWS_PROFILE I'm using to deploy with. There isn't a "access Pulumi state" profile. So if profile A creates stack DEV, and profile B creates stack TEST in the same location, the two files are put (s3:PutObject) using different AWS roles. Which means they can't (by default) read each others' stack: I can't use StackReferences.

I'm considering changing from using the default provider for all my resources, to explicitly providing one. This will allow me to always use a single AWS_PROFILE for Pulumi (bypassing the

bucket-owner-full-control

issue from a previous thread) while still using the correct profile for creating resources. When I change from using the default provider to using a provider with the same configuration, Pulumi wants to recreate all my resources. I don't want that (don't delete my RDS and AD!). Can I either - get the default provider and explicitly use it when appropriate, or - ignore the change in provider, or - change the way I'm creating my new-explicit-but-same-as-default provider so that Pulumi doesn't register a difference?

General question, how well does pulumi scale? If i have a config file with an array of 2000 objects, then create 1 resource per object This is in AWS, I can see the API being throttled maybe

For the GCP cloud functions, is there a way to create a function with the pubsub trigger like:

triggerTopic

?

https://github.com/pulumi/pulumi-gcp/issues/403 - this is multicloud issue, can someone from core team take a look at this?

I'm looking to perform ECS updates across 3 AWS regions as part of my deployment process. Is there a best practise/pattern for this sort of thing?

How does

.pulumi/ci.json

work when you have multiple projects in a single repository? Is there a ci.json reference/spec?

Hello cool ppls! Anybody help me understand how to interpolate output values into a string? Something like this:

podAssumeRolePolicyDocument = JsonConvert.SerializeObject(new
			{
				Version = "2012-10-17",
				Statement = new dynamic[]
				{
					new
					{
						Action = "sts:AssumeRole",
						Principal = new
						{
							Service = "<http://ec2.amazonaws.com|ec2.amazonaws.com>"
						},
						Effect = "Allow",
						Sid = ""
					},
					new
					{
						Sid = "",
						Effect = "Allow",
						Principal = new
						{
							AWS = Output.Create(eksNodeGroupRole).Apply(x => x.Arn.ToString())
						},
						Action = "sts:AssumeRole"
					}
				}
			});

the

Output.Create(eksNodeGroupRole).Apply(x => x.Arn.ToString()

just produces an empty string

We've been using pulumi with Google Cloud a bit, but having questions around some things. Anyone deal with Container Optimized images? For some reason, all references to Google images seem to be failing. Did something change here?

More specifically: For gcp.compute.Instance, the bootDisk.initializeParams.image setting. Ideally, we'd just use the 'cos-stable' family, but using a family here or specific image doesn't seem to work.

Hey folks, I’ve been following the docs to try to setup an EC2 cluster that auto-scales. https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#clusters And for some reason I’m getting this error when I do

pulumi up

aws:cloudformation:Stack (hello-autoscaling-group):
  error: 1 error occurred:
  * creating urn:pulumi:dev::pulumi-quickstart::awsx:x:ecs:Cluster$awsx:x:autoscaling:AutoScalingGroup$aws:cloudformation/stack:Stack::hello-autoscaling-group: ROLLBACK_COMPLETE: ["The following resource(s) failed to create: [Instances]. . Rollback requested by user." "Property AvailabilityZones cannot be empty."]

Here’s the relevant code:

const name = "hello";

const vpc = awsx.ec2.Vpc.getDefault();
const cluster = new Cluster(`${name}-cluster`, { vpc });

const asg = cluster.createAutoScalingGroup(`${name}-autoscaling-group`, {
  templateParameters: { minSize: 2, maxSize: 10 },
  launchConfigurationArgs: { instanceType: "t2.micro" },
});

Any idea what’s going on? I’m trying to just use

us-east-1

for everything to keep things simple. Thanks!