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
# Value Provider for Terraform [](https://github.com/pseudo-dynamic/terraform-provider-value/releases)[](./LICENSE)
2
2
3
-
A terraform provider providing resources to work with values. :smile:
3
+
A terraform provider providing resources to work with values. :smile:
Copy file name to clipboardExpand all lines: docs/resources/is_fully_known.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ subcategory: ""
5
5
description: |-
6
6
Allows you to have a access to result during plan phase that states whether value or any nested attribute is marked as "(known after apply)" or not.
7
7
Provider Metadata
8
-
Each module can use provider_meta. Beware that these settings only count for resources of this module. (see https://www.terraform.io/internals/provider-meta):
8
+
Each module can use provider_meta. Please keep in mind that these settings only count for resources of this module! (see https://www.terraform.io/internals/provider-meta):
9
9
terraform
10
10
// Terraform provider_meta example
11
11
terraform {
@@ -20,16 +20,16 @@ description: |-
20
20
seed_prefix (String) It gets appended to each seed of any value_is_fully_known (resource) or value_is_known (resource) within the same module.
21
21
Placeholders:
22
22
"{workdir}" (Keyword) The actual workdir; equals to terraform's path.root. This placeholder is
23
-
recommended because this value won't be drag along the plan and apply phase in comparison to
24
-
abspath(path.root) that you would add to resource seed where a change to path.root would be
23
+
recommended because this value won't be dragged along the plan and apply phase in comparison to
24
+
"abspath(path.root)" that you would add to resource seed where a change to path.root would be
25
25
recognized just as usual from terraform.
26
26
---
27
27
28
28
# value_is_fully_known (Resource)
29
29
30
30
Allows you to have a access to `result` during plan phase that states whether `value` or any nested attribute is marked as "(known after apply)" or not.
31
31
## Provider Metadata
32
-
Each module can use provider_meta. Beware that these settings only count for resources of this module. (see https://www.terraform.io/internals/provider-meta):
32
+
Each module can use provider_meta. Please keep in mind that these settings only count for resources of this module! (see https://www.terraform.io/internals/provider-meta):
33
33
```terraform
34
34
// Terraform provider_meta example
35
35
terraform {
@@ -45,8 +45,8 @@ terraform {
45
45
46
46
**Placeholders**:
47
47
- "{workdir}" (Keyword) The actual workdir; equals to terraform's path.root. This placeholder is
48
-
recommended because this value won't be drag along the plan and apply phase in comparison to
49
-
abspath(path.root) that you would add to resource seed where a change to path.root would be
48
+
recommended because this value won't be dragged along the plan and apply phase in comparison to
49
+
"abspath(path.root)" that you would add to resource seed where a change to path.root would be
Copy file name to clipboardExpand all lines: docs/resources/is_known.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ subcategory: ""
5
5
description: |-
6
6
Allows you to have a access to result during plan phase that states whether value marked as "(known after apply)" or not.
7
7
Provider Metadata
8
-
Each module can use provider_meta. Beware that these settings only count for resources of this module. (see https://www.terraform.io/internals/provider-meta):
8
+
Each module can use provider_meta. Please keep in mind that these settings only count for resources of this module! (see https://www.terraform.io/internals/provider-meta):
9
9
terraform
10
10
// Terraform provider_meta example
11
11
terraform {
@@ -20,16 +20,16 @@ description: |-
20
20
seed_prefix (String) It gets appended to each seed of any value_is_fully_known (resource) or value_is_known (resource) within the same module.
21
21
Placeholders:
22
22
"{workdir}" (Keyword) The actual workdir; equals to terraform's path.root. This placeholder is
23
-
recommended because this value won't be drag along the plan and apply phase in comparison to
24
-
abspath(path.root) that you would add to resource seed where a change to path.root would be
23
+
recommended because this value won't be dragged along the plan and apply phase in comparison to
24
+
"abspath(path.root)" that you would add to resource seed where a change to path.root would be
25
25
recognized just as usual from terraform.
26
26
---
27
27
28
28
# value_is_known (Resource)
29
29
30
30
Allows you to have a access to `result` during plan phase that states whether `value` marked as "(known after apply)" or not.
31
31
## Provider Metadata
32
-
Each module can use provider_meta. Beware that these settings only count for resources of this module. (see https://www.terraform.io/internals/provider-meta):
32
+
Each module can use provider_meta. Please keep in mind that these settings only count for resources of this module! (see https://www.terraform.io/internals/provider-meta):
33
33
```terraform
34
34
// Terraform provider_meta example
35
35
terraform {
@@ -45,8 +45,8 @@ terraform {
45
45
46
46
**Placeholders**:
47
47
- "{workdir}" (Keyword) The actual workdir; equals to terraform's path.root. This placeholder is
48
-
recommended because this value won't be drag along the plan and apply phase in comparison to
49
-
abspath(path.root) that you would add to resource seed where a change to path.root would be
48
+
recommended because this value won't be dragged along the plan and apply phase in comparison to
49
+
"abspath(path.root)" that you would add to resource seed where a change to path.root would be
0 commit comments