Open bcsgh opened 4 years ago
I'd also love to see the evaluated expressions provided for known values ; would be great to have a way to see what parts of your planned state are down to expressions you provided, and also what parts emerge from defaults, calculated / implied values, etc.
+1 From me.
It is always good to have a little more predictability.
Why isn't there more love for this bug affecting everyone :( ?
When I have to review policy it's impossible to understand what will be deployed.
Current Terraform Version
Use-cases
While running a
terraform plan
that will create multiple interconnected resources it is common to get(known after apply)
as the value for some of those interconnects.While that is technically correct it is significantly less useful than it could be. In my case, and in most cases, humans don't actually care about the identifier that will be filed in but rather which things it points to. In the case where that things is something else that terraform is going to crate, transform generally already has a meaningful name for it: the name of the things to be created that the name will be extracted from. It would be nice if terraform would include that in the output.
Attempted Solutions
n/a
Proposal
Append the un-evaluated expression resulting in "(known after apply)". There are likely cases where some special cases can do ever better, but the text of the expression would server as a good baseline.