When it comes to stack references, what are people...
# golang
m
When it comes to stack references, what are people doing to enforce that an output exists before continuing? From my tests i simply get a
nil
value if I reference an output that doesn't exist. Also, if I have a folder structure like this:
Copy code
root
  infra
  app
And my
app
project references resources from the
infra
project, is there a way I can
pulumi up
the entire directory rather than running it from the individual folders/projects? Or would I need to look into the automation API for that?
b
you can check the value inside an
apply
and then exit the program is it's not resolved
something like
pulumi.log.error
m
ooh, good idea. Thanks @billowy-army-68599