This message was deleted.

I think the primary reason is that the name of the target stack is an

Input<string>

, so could be something you compute as part of an output of another resource. This is certainly not the most common case though.

thanks, but this could make coding more complex, now I tried a quick hack:

import * as pulumi from '@pulumi/pulumi'

async function run() {
  const mainStackRef = new pulumi.StackReference(`stackRef-main`, {
    name: `mainStack`
  })
  const fixedIpSubnetIds: pulumi.Output<string[]> = mainStackRef.getOutput('fixedIpSubnetIds')

  const fixedIps: string[] = await new Promise((resolve, reject) => {
    fixedIpSubnetIds.apply(t => resolve(t))
  })

  console.log(fixedIps)
}

run()

It logs the ips, even during pulumi preview, I assume because that Output value already known. Can we rely on this behavior or this is not guaranteed?

FWIW - I think you can accomplish the same with just:

fixedIpSubnetIds.apply(t => console.log(t))

I'm not positive you can also rely on the code as you wrote it - for example, during previews - though I expect that you can. Is your real use case more complex than

console.log

? I'd be interested to see more of it to understand how you want to use the value from the

StackReference

.

Yes, it's more complex, it's just a small example, this connects to an earlier conversation: https://pulumi-community.slack.com/archives/C84L4E3N1/p1551129344303800