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!

how can I get Internet Gateway ID from

const default_vpc = awsx.ec2.Vpc.getDefault(); 
      console.log(default_vpc.internetGateway.id)

Got error

'resourceGroupName' is not defined

for Azure ARM template deployment

File "./__main__.py", line 23, in <module>

resourceGroupName: resource_group.name,

NameError: name 'resourceGroupName' is not defined

error: an unhandled error occurred: Program exited with non-zero exit code: 1

part of code here, not sure where to look for

TemplateDeployment

docs , can't see them in API reference

armDeployment = azure.core.TemplateDeployment("test-dep", {

resourceGroupName: resource_group.name,

templateBody: JSON.stringify(content),

parameters: {

"storageAccountType": "Standard_GRS",

},

deploymentMode: "Incremental",

})

I've got some mismatches with my AWS NACLs and NACL rules, which mostly haven't changed in AWS or my project: a few rules are deleted, and I think the rule names may have changed (but they're not in AWS, just in the state, so that shouldn't matter?).

pulumi  refresh

wants to delete all my NACLs and rules from state, and not update anything. That will leave a pile of good(ish) NACLs and rules in AWS, and Pulumi won't be able to manage them. How can I recover? I can't see anything in

pulumi stack --help

or

pulumi state --help

that meets my needs. There's a few options that would help if they were possible: updating the state to match reality, importing reality from AWS into the state, or deleting the NACs and rules from AWS so that reality matches state. Which is the best, and how do I do it?

New topic: is this a bug? I'm importing a resource (AWS VPC peering connection) that is defined inside my own ComponentResource. I accidentally passed the

{ import: 'pcx-xyzabc123' }

opt to the ComponentResource constructor instead of to the

aws.ec2.VpcPeeringConnection

constructor. This failed because now it's trying to import all resources with the same id (because the opts that I pass to my ComponentResource gets passed to all the nested resources). So I fixed that. Now when I run preview, it says it'll import my VpcPeeringConnection fine, but it's still trying to import the other resources! Even when I remove the

import:

altogether, it's still trying to import! The specific error message is like this:

error: Preview failed: importing pcx-075eac9319f99ebd2: unexpected format of ID ("pcx-xyzabc123"), expected NETWORK_ACL_ID:RULE_NUMBER:PROTOCOL:EGRESS

New new topic: providers and invoke calls. I'm not getting the expected caller ID back from this:

const provider = new aws.Provider('x", { region: 'us-east-1', profile: 'assumed-role-in-acct-FOO'});
const identity = aws.getCallerIdentity({ provider: provider});

The returned

identity

is the one from the default provider. I expect to see a different arn, accountId and userId in there. Am I doing something wrong?

hi to all, is there a java binding to pulumi

i have two stacks, one for production and one for testing. the testing environment is 100% managed by pulumi. the production environment is only partially managed by pulumi (it existed before we started using pulumi and we are slowly bringing all resources over to being managed by pulumi). how should we manage some resources being managed in only one environment? two index files? we are using typescript

Hey everyone. Is there a way to run pulumi up/preview through a go api? we have many stacks and on release we run pulumi up on all stacks but we would like to get some more control by moving away from bash scripting for that. what would be even more awesome would be a meta stack that allows to controll the other stacks 🙂 pulumiception

@white-balloon-205 Hi, what is a road map for

pulumi logs

command. https://www.pulumi.com/blog/unified-logs-with-pulumi-logs/ In this article you mentioned that K8s will be also supported. Do you have some idea when this might happen?

Quick question: I can’t seem to find any mention of

rollback

in your docs. Does Pulumi support rollback on failed deploys, and if not, do you plan to support it at some point in the future? Thanks!

Hi I'm Grant and excited to join the Pulumi Slack org.

Hi, I noticed that in the code blocks in the ECS docs,

FargateTaskDefinition

is used twice (instead of

EC2TaskDefinition

), same goes for

FargateService

, which is used twice instead of

EC2Service

. https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#task-definitions https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/#services Overall the docs have been very helpful. Thanks for updating!

hi everyone, I was looking to implement a component package like this one: https://www.pulumi.com/blog/creating-and-reusing-cloud-components-using-package-managers/ but i would like to attempt it in python. Does anyone have a resource or a project to share that could help me out to get started?