A quick questions about multiple Output lt string gt in an a

Question

A quick questions about multiple Output lt string gt in an array Input lt string gt ```Envs = new Input lt string gt Analytics DB ANALYTICS DB USERNAME=postgres ANALYTICS DB PASSWORD=password analyticsPostgresHostname Accounts DB ACCOUNTS DB USERNAME=postgres ACCOUNTS DB PASSWORD=password accountsPostgresHostname ACCOUNTS DB PORT=5432 ANALYTICS DB PORT=5431 PORT=80 ``` Where both the `analyticsPostgresHostname` and `accountsPostgresHostname` are defined like ``` var accountsPostgresHostname = accountsPostgresContainer Hostname Apply networkName = gt $ ACCOUNTS DB HOSTNAME= networkName var analyticsPostgresHostname = analyticsPostgresContainer Hostname Apply networkName = gt $ ANALYTICS DB HOSTNAME= networkName ``` However only one of those hostnames actually get filled the other is an empty string Is it expected that both those Output lt string gt be resolved in that Input lt string gt I appreciate your time

echoing-dinner-19531 · Answer

Yes it is expected that both of those would resolve

clever-glass-42863 · Answer

< echoing dinner 19531> thanks for the response Only one of the values propagates while both containers spin up prior to the one that is assigned these environment variables What are the best next steps in debugging this

echoing-dinner-19531 · Answer

I d check the state of both resources via `pulumi stack export` to see if the output value is filled in for the resource

clever-glass-42863 · Answer

< echoing dinner 19531> from the `pulumi stack export` we can see that Apply call is being made yet networkName is null See this output from that variable ``` ACCOUNTS DB HOSTNAME= ``` That would only be set if the Apply call was invoked yet the value should come from the parameter being fed in via the Apply ```var accountsPostgresHostname = accountsPostgresContainer Hostname Apply networkName = gt $ ACCOUNTS DB HOSTNAME= networkName ```

clever-glass-42863 · Answer

< echoing dinner 19531> Just an update for anyone else running into this I had to `pulumi rm` the entire stack and recreate locally for this to work as expected Not sure what state the local containers go into considering they were being recreated however after doing so both hostnames populate as expected

echoing-dinner-19531 · Answer

Hmm sounds like a provider bug If you hit this again can you raise a bug on the docker provider repo