Skip to content
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.

Provider fails if it can’t ping a non-yet-provisioned influxdb instance #9

Open
paulgrav opened this issue Jul 26, 2018 · 0 comments

Comments

@paulgrav
Copy link

The influxdb Terraform provider attempts to sanity check and ping test the url value in the provider block. This is problematic when Terraform has even begun to provision a influxdb instance.

I think any checking/pinging should be delayed until the influxdb resources are run.

Terraform Version

Terraform v0.11.7

  • provider.azurerm v1.11.0
  • provider.grafana v1.0.2
  • provider.influxdb v1.0.1
  • provider.random v1.3.1

Affected Resource(s)

provider "influxdb"

Terraform Configuration Files

provider "influxdb" {
  url      = "http://${azurerm_container_group.hydra-loadtestdb-cg.ip_address}:8086"
  username = "admin"
  password = "${random_string.influx_admin_pass.result}"
}

Debug Output

https://gist.github.com/paulgrav/620793871695c4f8c6298beb36120730

Expected Behavior

Provider should not assume that an InfluxDB has already been provisioned. InfluxDB resources should begin provisioning once dependencies have completed.

Actual Behavior

Provider attempts to ping test an InfluxDB has has yet been provisioned. Terraform apply command fails.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply

Important Factoids

n/a

References

n/a

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant