-
### Language Server Version
v0.32.4
### Terraform Version
1.6.6
### Client Version
VS Code 1.85.0
### Terraform Configuration
```terraform
terraform {
required_providers {
tfe = {
…
-
Bug Description
We are currently using Terraform Enterprise (TFE) to manage Terraform in multiple accounts. Theres is a central TF role in the TF build account. Then there are terraform roles in ever…
-
#### Use-cases
Please add the ability to configure Run Tasks with the recently introduced stage `post_apply`. The ability to configure this stage in TFE was released in [v202402-1](https://…
-
It seems that the TFE token generated from resource `vault_terraform_cloud_secret_creds` cannot be used in the TFE provider.
The root cause is most likely due to the fact that the TFE provider is n…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
Originally raised as https://github.com/leg100/otf/issues/614
so the idea is, linking workspaces together and 1 workspace trigger the next, like in:
https://registry.terraform.io/providers/hashi…
-
#### Terraform Cloud/Enterprise version
tfe v0.49.0
#### Terraform version
```plaintext
Terraform v1.3.4
```
#### Terraform Configuration Files
```terraform
terraform {…
-
### Feature description 💡
I see that we can configure: `.Values.ingress.api.path`, `.Values.ingress.registry.path` and `.Values.ingress.dex.path` but not sure how to configure custom path for particu…
-
### Terraform Core Version
1.5.1
### AWS Provider Version
5.0
### Affected Resource(s)
aws_elasticache_subnet_group
aws_elasticache_replication_group
### Expected Behavior
Update…
-
Using TFE on premise behind a company proxy.
On Applying plan, we get the error below:
`Error: Post "https://api.github.com/user/repos": dial tcp 140.82.121.5:443: connect: connection timed out`
…