Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
bulky-yacht-13037
08/24/2022, 2:58 PMRelated 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/><TEAM>/<PROJECT>"p
powerful-lunch-15492
08/24/2022, 4:35 PMs3 will make all path automagically. but for
file://❤️ 1
b
bulky-yacht-13037
08/24/2022, 4:39 PMThanks!