No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Related with FQNs not being (yet) supported for some backends like AWS S3; are there any alternatives anyone has been using to deal with this (i.e. diff buckets per projects; sub dirs inside the same bucket; etc) as a workaround? Or any suggestions?

I’ve figured the sub dirs option could be a good workaround (ex.: `"<s3://backend/>&lt;TEAM&gt;/&lt;PROJECT&gt;"`). I’d have to create my own discovery mechanism for teams/projects/stacks tho :thinking_face:

s3 will make all path automagically. but for `file://`  you have to make all dirs