terraform-provider-http icon indicating copy to clipboard operation
terraform-provider-http copied to clipboard

Utility provider for interacting with generic HTTP servers as part of a Terraform configuration.

Results 55 terraform-provider-http issues
Sort by recently updated
recently updated
newest added
trafficstars

pull request

documentation
size/XL

_This issue was originally opened by @tomdavidson as hashicorp/terraform#5848. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._ I would...

enhancement

### Terraform CLI and Provider Versions ``` terraform version Terraform v1.2.6 on darwin_amd64 ``` ### Use Cases or Problem Statement The current version of this provider does not expose an...

enhancement

Given a URL that serves `application/zip` content (or some other archive content), I would like to be able to reference it in other resources that require it (see example below)....

enhancement

When using the http data source with Accept = "application/vnd.docker.distribution.manifest.v2+json" request header, we are receiving Content-Type warnings. Shouldn't "application/*+json" Content-Types be treated the same as application/json? ### Terraform Version Terraform...

Hello, I believe the issue is that XML content type is not allowed in the return. ### Terraform Version Terraform v0.14.9 ### Affected Resource(s) - data.http ### Terraform Configuration Files...

### Terraform Version Terraform v0.14.8 provider registry.terraform.io/hashicorp/http v2.1.0 ### Affected Resource(s) - data http ### Terraform Configuration Files ```hcl data "http" "cert_manager" { url = "https://github.com/jetstack/cert-manager/releases/download/v1.2.0/cert-manager.yaml" } output "content" {...

This refers to PEM encoded files often used for certificates and related data. Example source for this content type: https://github.com/ietf-wg-acme/acme/issues/120

size/XS

_This issue was originally opened by @MarcelT-NL as hashicorp/terraform#23389. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._ ### Current...

### Terraform CLI and Provider Versions ``` $ terraform version Terraform v1.1.8 on darwin_amd64 ``` ``` provider "registry.terraform.io/hashicorp/http" { version = "2.2.0" } ``` ### Use Cases or Problem Statement...

enhancement