This message was deleted.
# general
s
This message was deleted.
w
Yes - this is definitely a place where things feel a little less consistent around the `Input`/`Output` model - and we should think about making another change here. The original rationale for going this direction is (partly) covered here: https://github.com/pulumi/pulumi-terraform/issues/204#issuecomment-404611183 Technically these APIs don't need to track dependency information, and thus they don't have to use `Input`/`Output`. And by making them accept normal values and return
Promises
, you are technically provided more flexibility to combine these in ways that `Input`/`Output` would not support. But the resulting ergonomics for the common case are unfortunately less consistent - and the code to use them a little less "simple". So I do want to look into this again.