Skip to content

Disabled Icingaweb2 Modules should be getting installed anyways #404

@MisterMountain

Description

@MisterMountain

I currently try to install an icingaweb2 module, ship it with some preconfiguration, but i want to have it disabled for the start anyways.
For example i got this codeblock in my vars:

icingaweb2_modules:
  icingadb:
    enabled: false
    source: "package"
    commandtransports:
      icinga2:
        transport: "api"
        host: "localhost"
        port: "5665"
        username: "foobar"
        password: "barfoo"
    config:
      icingadb:
        resource: "icingadb"
      redis:
        tls: "0"
    redis:
      redis1:
        host: "localhost"

In this case the Installation of the icingadb module would be skipped, and thus the module would also not get configured.
I would have expected that the collection installs the package, configures icingadb-web and then disables it.
I believe it might be to one of the conditions here:

when: icingaweb2_modules is defined and icingaweb2_module_packages[item.key] is defined and item.value.enabled | bool == true and item.value.source == "package"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions