Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

icinga2 Provider, Host resource bug #14819

Closed
robrankin opened this issue May 25, 2017 · 1 comment
Closed

icinga2 Provider, Host resource bug #14819

robrankin opened this issue May 25, 2017 · 1 comment

Comments

@robrankin
Copy link
Contributor

The Icinga2 Host resource creates an Icinga2 Host object as follows:

object Host "host" {
	action_url = ""
	address = "192.168.1.1"
	address6 = ""
	check_command = "hostalive"
	display_name = ""
	groups = null
	notes = ""
	notes_url = ""
	templates = null
	vars = {
		something = "blart"
	}
	version = 1495628446.109900
	zone = "master"
}

The groups = null syntax does not appear to be valid. When attempting to use Icinga2's group assign functionality, assign where, to assign the above Host object to Hostgroup object, the groups = null entry causes Icinga2 to segfault.

As far as I can tell so far it's only acceptable for the groups parameter to have a non-empty list of 1 or more members.

groups = ["",] does not work for example.

Icinga2 bug report here: Icinga2 Issue #5288

Terraform Version

Terraform v0.9.4

Affected Resource(s)

Please list the resources as a list, for example:

  • icinga2_host

Terraform Configuration Files

resource "icinga2_host" "host" {
  hostname      = "${var.hostname}"
  address       = "${var.address}"
  check_command = "${var.checkCommand}"

  vars {
    something = "blart"
  }
}

Expected Behavior

The Icinga2 Host resource creates correct Icinga2 object syntax

Actual Behavior

The Icinga2 Host resource creates incorrect Icinga2 object syntax

Steps to Reproduce

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

  1. terraform apply

References

Icinga/icinga2#5288

@ghost
Copy link

ghost commented Apr 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants