Radek Simko
Radek Simko
## Background Terraform supports a number of [operators](https://www.terraform.io/docs/language/expressions/operators.html), which can be combined with other expressions, for example: - `1 + 2 * 3` - `(1 + 2) * 3` -...
## Use-cases Support for traversals was added in https://github.com/hashicorp/terraform-ls/pull/485 - which introduced support for _simple_ index expressions the element is a reference and key is static (either number or string),...
## Background Support for scoped/absolute traversals, where the collection being indexed is a static traversal was added in #485 - this brought support e.g. for `aws_instance.example.tags["owner"]` or `aws_alb.example.access_logs[0]`. However Terraform...
## Use-cases Terraform supports a number of [expressions](https://www.terraform.io/docs/language/expressions/index.html) (such as function calls, arithmetic operators, references etc.). While expressions help users achieve and increase readability of their configurations they can make...
## Use-cases Terraform supports [a `dynamic` "meta" block](https://www.terraform.io/docs/language/expressions/dynamic-blocks.html) within `resource` `data`, `provider` and `provisioner` blocks, for example: ```hcl resource "aws_elastic_beanstalk_environment" "example" { name = "example" application = "example-app" solution_stack_name =...
## Background Terraform supports `each.key` and `each.value` references within `resource`, `data` or `module` block and anywhere where [`for_each` meta-argument](https://www.terraform.io/language/meta-arguments/for_each) is supported, for example ```hcl resource "azurerm_resource_group" "rg" { for_each =...
## Background Terraform supports `self.` references within `provisioner` and `connection` resource blocks, such as ```hcl resource "aws_instance" "web" { # ... provisioner "local-exec" { command = "echo The server's IP...
## Notes https://github.com/hashicorp/terraform-ls/issues/583 is not a dependency, but `count.index` is quite frequently used as string in various names/tags and so is important in the context of this issue. ## Background...
Currently the server will error if user hovers over, or requests completion in a position which has no data (e.g. near braces). The server shouldn't error, but return empty response...
## Background - TF Core Support of optional and default object attributes has been developed through various experiments over time. We currently don't reflect any of these in IntelliSense. ###...