This message was deleted.
# automation-apis
sparse-intern-71089
09/11/2021, 1:33 PMThis message was deleted.
b
bored-oyster-3147
09/11/2021, 10:09 PMYou can use a local backend and then explore the files. It’s the same as S3.
c
crooked-pillow-11944
09/11/2021, 10:26 PMRight - but my question still stands - how is project metadata placed in a custom backend (s3 or local)?
In my bucket I see directories for stacks, backups, and history
crooked-pillow-11944
09/11/2021, 10:28 PMFor now I'm just prepending my stacks with the project name
crooked-pillow-11944
09/11/2021, 10:30 PMMy problem has been that I've created multiple projects with the same stack name and the stack metadata is getting overwritten
b
bored-oyster-3147
09/12/2021, 6:21 PMSorry I misunderstood the specifics of what you were asking. Yes that is a known current limitation of all of the file-state backends.
See here: https://github.com/pulumi/pulumi/issues/2522
In Pulumi SaaS stack names are unique to the project. In file-state backends stack names are globally unique.
c
crooked-pillow-11944
09/12/2021, 6:30 PMThanks for the link. It's easy enough to workaround this (i.e. prepending the project name)