known after apply
What a plan shows for a value that cannot exist until apply, such as an identifier or checksum the provider will generate.
In more detail
Terraform is being honest: it does not invent values it cannot know. Anything computed from an unknown value is also unknown, and a data source whose input is unknown is read during apply instead of during plan.
Related terms
- terraform plan — The command that compares configuration, state and reality and prints the actions needed to make them match, without changing anything.
- resource attribute — A value you can read off a resource's address, either an argument you set or one the provider fills in, such as local_file.greeting.id.
- data source — A data block that asks a provider to look up an existing object and return its details, without Terraform creating or owning it.
Taught in
- Enforcing OPA Guardrails on Terraform Plan Payloads — Cloud Security & DevSecOps Engineering
- Predicting Changes, Then Applying Them — Infrastructure as Code with Terraform
- Querying Existing Infrastructure With Data Sources — Infrastructure as Code with Terraform
- Reading A Plan, Saving It, Applying It — HashiCorp Terraform Associate (004) Exam Prep
- Resources, Data Sources And The References Between Them — HashiCorp Terraform Associate (004) Exam Prep
- Count, For Each And Dynamic Blocks — HashiCorp Terraform Associate (004) Exam Prep