This message was deleted.
# aws
s
This message was deleted.
g
each project should have its own directory then stack reference path is
org/project/stack
e
@great-sunset-355 thanks for the response. But, I read that with S3 as backend,
org
is not defined. Or do you know how to get it? Also, with different paths (folders within the same bucket), tried to reference as
project/stack
. But got
unknown stack
, or something of the sort.
g
hmm I see, check out the structure of this project, it's pretty big and complex it may give you an answer https://github.com/mitodl/ol-infrastructure/blob/f42b329df70b4ec7c59295e0e011100a61775472/src/ol_infrastructure/infrastructure/mongodb/__main__.py#L28
It looks like you just use only the
stack_name
regardless of the project with S3 Here is a reference to the same stack but from a completely different directory https://github.com/mitodl/ol-infrastructure/blob/f42b329df70b4ec7c59295e0e011100a61775472/src/ol_infrastructure/applications/concourse/__main__.py#L40
e
Thanks! I’ll check that
l
I thought it wasn't possible to use StackReferences to stacks in a different file? That is, if you're using an S3 backend, everything has to have the same
backend
URL?
e
@little-cartoon-10569 are those questions, they sound like affirmations. From my limited testing, I couldn’t find a way for a given project to get a StackReference on a stack on a different folder. The only working model I could make, was with all the stacks on the same folder.