What's generally the way one would access Pulumi stack outputs in other non-Pulumi projects? For example I've got a CICD workflow where I want to push a new container image to a ECR repo. Said repo gets created by my Pulumi stack.. Any suggestions on how to pass along the details of that ECR repo to my workflow?

When organizing projects and stacks for core infrastructure resources (IAM, Guardduty, Cloudtrail) across all AWS accounts, is the preferred approach to have a single "infra" project that contains the resources that belong in each account and then have a stack in that project for each account ("root", "dev", "prod", "networking", "ops")? If so, what if you want to conditionally create resources in some accounts and not others, say a role in only the ops account and not the others? Are there downsides to wrapping resources with

if (config.accountName === "ops") {...}

or is that even possible? I'm coming from TF and am possibly trying to fit Pulumi to the patterns in TF and that may be a bad idea. Any guidance would be great!

Hi everyone, I am having hard time to understand the concept of stack. What I want to know is the way to setup different infrastructure for each stacks, i.e. dev, prod, test. As far as I know, if I want to define my infra in python, I have to write down everything in

__main__.py

. But this file doesn’t change when I switch between stacks(of course). What should I do? Should I use git? 😞

What is the Pulumi equivalent to Terraform modules? Component Resources? What about wrapping resources in a function and importing those into the main file and passing options to it?

any good way to troubleshoot a very long running

pulumi destroy

Are there any examples out there of large-scale, multi-account architectures? I've come across a lot of examples for small services and simple resource groupings, but setting up environments, accounts, permissioning across a provider like AWS or Azure would be really useful. Since Pulumi is so flexible, it seems like there is a need for more guidance at scale.

Who can help me setting Azure pipeline with self-hosted Pulumi state in Azure blob ?

hi all! I'd love to get some user feedback on this blog about understanding

apply()

- if you're struggling to understand, let me know if this helps! https://www.leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html

Hello there - I am using aws-typescript. Doing first basic provisioning of EC2 instances, and the name of the instances is not getting set on creation? I would assume the resource name is used as the VM name? no other args to tap into to be able to set the EC2 instances name either as far as I can tell.

Hey folks! I'm trying to use Pulumi in my organization and I'm a little messed with how to configure some AWS stuffs. In my case, I have a Lambda Function to be triggered by an event in S3. It's working pretty well, but I'd like to put Pulumi to create/deploy it. Is there a way to export my already configured Lambda Function so I could let Pulumi work in it?

hey all, I want to split up my index.ts main file into resource group files (e.g. database.ts and beanstalk.ts) And have the different files connect to each other using es6 imports When I tried this earlier it fails and only picks up index.ts for changes : / Is there a way I can make pulumi pick up changes for a folder? or even a collection of files?

👋 Quick question: what are the Azure role assignments needed for the Service Principal to be used with Pulumi? That is not clearly articulated in the Pulumi documentation from what I can make out. Thanks in advance!

What am I doing wrong?

❯ pulumi config set aws:region us-west-2
❯ pulumi config get aws:region
    us-west-2
❯ pulumi up

error: 1 error occurred:
    	* missing required configuration key "aws:region": The region where AWS operations will take place. Examples are us-east-1, us-west-2, etc.
    Set a value using the command `pulumi config set aws:region <value>`.

Are there any examples of what options I can pass to the

-c

option for starting a new pulumi project? example command

pulumi new aws-python -n test -c .....

I want to start a pulumi python project and configure the

main

and

venv

option in the Pulumi.yaml file at project creation.

I see in the help from

pulumi new

that

-c

accepts a stringArray but I can not figure this out.

Hello, My team is evaluating various infrastructure as code tools to enable management and expansion of our Cloud resources. We have gotten some smaller, individual workloads managed by Pulumi so far and we would like to realize case studies, examples, or templates for managing a multi-account, multi-cloud environment. We haven’t been able to find anything more than very general guidance. Unfortunately, this general guidance does not enable us to complete our evaluation to determine Pulumi’s ability to suit our needs. Who should we reach out to for help?

I've been struggling for the past few hours trying to deploy my code to Google Cloud Function. An internal library that we're using is causing

which could not be serialized because Cannot read property 'executionQueuePromise' of undefined

and other similar serialisation errors. I did get some success with the deploy when I used

import('./../dist/src/rpc/startTransaction.js')

inside the GCF handler, but now the

dist

directory is not uploaded as a dependency and is not present in the GCF (and it fails on request). How can I force Pulumi to include additional source files?

Hey everyone! I'm considering multi-cloud tools for an Electron app I'm developing which needs to facilitate users setting up cloud VM's through a GUI. I was considering Terraform but I don't want to have to bundle another binary in my app. It looks like Pulumi acts as a library, will it work for what I'm trying to do?

Hello teams! I'm just landed on Pulumi plantet! I'm follow the getting started guide, I've setup the aws cli and created the aws-typescript project but when I do pulumi up I get this error: SyntaxError: eval at <anonymous> (/home/dometec/test/pulumi/node_modules/@pulumi/pulumi/runtime/closure/v8_v10andLower.js8227)17 Expected an operand but found %    return %FunctionGetScriptSourcePosition(func);

I've tried on two linux machine and I get the same error, node version is v12.20.1 and pulumi ver is v3.2.1

any help?

is there any way to disable function serialization?

I have a multiple region project in AWS - but Pulumi seems to only take one region via config. Does this mean I need a different stack for each region? So dev.us-east-1, dev.us-west-1, prod.us-east-1, etc etc ?

Is there any way to force and output to a str. I ran into this error when passing

extra_args

to the docker local

Image

buider:

File ".../venv/lib/python3.9/site-packages/pulumi_docker/docker.py", line 574, in get_command_line_message
        argstr = " ".join(args) if report_full_command_line else args[0]
    TypeError: sequence item 2: expected str instance, Output found
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

The output should have already been resolved, so all I really want is the way to access the result/value

Code is roughly:

image_name = <<Output>>

image = Image(
    "image",
    image_name=image_name,
    build=DockerBuild(
        context="..",
        extra_options=["--cache-from", image_name],
    ),

)

🙋 Roll call! Who else is here? I need help

Hey guys, we recently started implementing Pulumi as IaC for our organization. I was creating Aure cache for redis using

azure-native

module & couldn't find a way to specify that I want redis version 6.0.3 and by default it creates redis version 4.0.14. Can someone please help?

👋 Hi all, heard about Pulumi via a podcast a while back and finally tried it out against Terraform (which I've no experience with either) yesterday. Pulumi is a winner so far! Nice to meet everyone, look forward to getting more involved!

Hi everyone, i new in pulumi i have this basic code to deploy a fargate cluster but i need to add to the task a permission to access a dynamodb table, how can I do it?

import * as pulumi from "@pulumi/pulumi";
import * as awsx from "@pulumi/awsx";

// Create a load balancer to listen for requests and route them to the container.
const listener = new awsx.elasticloadbalancingv2.NetworkListener("bff-meds", { port: 8888 });

// Define the service, building and publishing our "./app/Dockerfile", and using the load balancer.
const service = new awsx.ecs.FargateService("bff-meds", {
  desiredCount: 2,
  taskDefinitionArgs: {
      containers: {
          nginx: {
              image: awsx.ecs.Image.fromPath("bff-meds", "./app"),
              memory: 512,
              portMappings: [listener],
          },
      },
  },
});

// Export the URL so we can easily access it.
export const frontendURL = pulumi.interpolate `http://${listener.endpoint.hostname}/`;