make LookupEnv use cached v parameter

[lock14]

No description provided.

[sethvargo]

This is actually intentional; we don't lock, so we want to create the local allocation in case the underlying variables changes beneath us. You cannot guarantee that the c.stdout on L1 is the same c.stdout that you return.

[pdewilde]

Oops, that wasn't the "delete draft button"

[lock14]

This is actually intentional; we don't lock, so we want to create the local allocation in case the underlying variables changes beneath us. You cannot guarantee that the c.stdout on L1 is the same c.stdout that you return.

I see, that makes sense. Shouldn't LookupEnv method also use the v parameter then? I've updated the code to do this.