You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some situations, it is possible to determine where the data in a field that is marked as "(known after apply)" is coming from. A good example is creating an EC2 instance and a security group. We won't know the security group ID until we create it and therefore we won't know the list of security groups for that instance until the security group has been created. However, we do know that the list of security groups for that instance will contain the ID of the security group that we are creating and if we can show that to users it will help them to understand what is actually going on. Also, we might be able to extract relationships from these things which could be useful.
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the
following symbols:
+ create
Terraform will perform the following actions:
# terraform_data.one will be created
+ resource "terraform_data" "one" {
+ id = (known after apply)
+ input = "hello world"
+ output = (known after apply)
}
# terraform_data.two will be created
+ resource "terraform_data" "two" {
+ id = (known after apply)
+ input = (known after apply)
+ output = (known after apply)
}
Plan: 2 to add, 0 to change, 0 to destroy.
The problem here is that terraform_data.two just says that its input will be (known after apply). Where it would be much more useful if we knew that the input was from terraform_data.one.output as we could infer what that meant. It would be good if we could change the text that we added here to be something like (known after apply) From: terraform_data.one.output
In some situations, it is possible to determine where the data in a field that is marked as "(known after apply)" is coming from. A good example is creating an EC2 instance and a security group. We won't know the security group ID until we create it and therefore we won't know the list of security groups for that instance until the security group has been created. However, we do know that the list of security groups for that instance will contain the ID of the security group that we are creating and if we can show that to users it will help them to understand what is actually going on. Also, we might be able to extract relationships from these things which could be useful.
For example if we look at the following code:
We get the following plan:
The problem here is that
terraform_data.two
just says that its input will be(known after apply)
. Where it would be much more useful if we knew that the input was fromterraform_data.one.output
as we could infer what that meant. It would be good if we could change the text that we added here to be something like(known after apply) From: terraform_data.one.output
Here is the full JSON plan for reference:
The text was updated successfully, but these errors were encountered: