This message was deleted.

Would something like this work?

import json
from pulumi_aws import s3

with open("buckets.json") as bucket_data:
    buckets = json.load(bucket_data)

for bucket in buckets:
    s3.Bucket(bucket)

... where

buckets.json

just contains a JSON array of strings:

[
    "one",
    "two",
    "three"
]

• I looked into using

os.getcwd()

but unfortunately, pulumi changes the current directory to the program directory so it does not give an accurate value 😞 Using the project structure below, if I am inside the

configs/dev

directory when I run

pulumi up

, if I add

print(os.getcwd())

inside the

__main__.py

, it returns the path to the

src

folder and not the configs folder • Your example works because the

Pulumi.yaml

and the python program are in the same folder. I guess that's on me for not being more detailed 😄 This is my project structure:

├── configs
│   ├── dev
│   │   ├── Pulumi.main.yaml
│   │   ├── Pulumi.yaml
│   │   └── auth0-users.yaml
├── requirements.txt
└── src
    ├── __init__.py
    ├── __main__.py
    ├── __pycache__
    ├── auth0_database.py

and the

Pulumi.yaml

file has

main: ../../src

attribute

There may be options for adjusting some of this at the project file level -- e.g., here: https://www.pulumi.com/docs/concepts/projects/project-file/#attributes

> If the users yaml/json file is truly infra config, you might also consider just putting that data right into one of the Pulumi YAML files I thought about this but I did not want to bundle all the configuration inside the one yaml file because it'd make it quite big and difficult to maintain 😕 --- so far the only option I found is the use

os.getcwd()

inside

__main__.py

and manually compute the path back to the configs folder like:

../configs/dev

where

dev

would be stored in a variable so I can dynamically adjust the path

Yeah -- I mean the Python program isn't running in the

configs

folder, it's running in the

src

folder, so this makes sense, relative to where the program code is

I'm sad that pulumi clearly knows this path (it uses it to compute the absolute path when using

FileAsset

resource) but does not expose it anywhere 😞 Maybe I could open a feature request for this

You bet! Always fun trying to make these things work 🙂