Legacy dot index syntax TF-L0038
Bug risk
Major
2 days ago
—
a year old
List items should be accessed using square brackets
95
96 spec {
97 automount_service_account_token = true
98 service_account_name = kubernetes_service_account.api.metadata.0.name 99 share_process_namespace = true
100 priority_class_name = "system-cluster-critical"
101List items should be accessed using square brackets
29 subject {
30 kind = "ServiceAccount"
31 name = kubernetes_service_account.api.metadata.0.name
32 namespace = kubernetes_service_account.api.metadata.0.namespace 33 }
34}
35List items should be accessed using square brackets
28
29 subject {
30 kind = "ServiceAccount"
31 name = kubernetes_service_account.api.metadata.0.name 32 namespace = kubernetes_service_account.api.metadata.0.namespace
33 }
34}List items should be accessed using square brackets
23 role_ref {
24 api_group = "rbac.authorization.k8s.io"
25 kind = "ClusterRole"
26 name = kubernetes_cluster_role.api.metadata.0.name 27 }
28
29 subject {List items should be accessed using square brackets
1output "endpoint" {
2 depends_on = [kubernetes_service.resolver]
3 value = kubernetes_service.resolver.spec.0.cluster_ip 4}
5
6output "selector" {
Description
Terraform v0.12 supports traditional square brackets for accessing list items by index.
However, for backward compatibility with v0.11, Terraform continues to support accessing list items with the dot syntax normally used for attributes.
While Terraform does not print warnings for this syntax, it is no longer documented and its use is discouraged.
It is therefore recommended to switch to the square bracket syntax when accessing items in list, including resources that use count.
Example:
locals {
list = ["a", "b", "c"]
value = list.0
}