Document ApiUser not deployed

[tonnenpinguin]

Expected Behavior

When adding an ApiUser Object with Director it should be added to the icinga2 configuration.

Current Behavior

When adding the ApiUser Object with director I can see it within director, but during deployment log still says information/ConfigItem: Instantiated 1 ApiUser. (the root user). I also tried to grep within the /var/lib/icinga2 and /etc/icinga2 directories for the ApiUser, but the newly created ApiUser doesn't show up.

Steps to Reproduce (for bugs)

• Go to director -> infrastructure -> Api User.
• Add ApiUser
• Deploy configuration

Your Environment

• Director version (System - About): current master
• Icinga Web 2 version and modules (System - About): 2.5.3
• Icinga 2 version (icinga2 --version): icinga2 - The Icinga 2 network monitoring daemon (version: r2.8.4-1)

Copyright (c) 2012-2017 Icinga Development Team (https://www.icinga.com/) License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/gpl2.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

Application information: Installation root: /usr Sysconf directory: /etc Run directory: /run Local state directory: /var Package data directory: /usr/share/icinga2 State path: /var/lib/icinga2/icinga2.state Modified attributes path: /var/lib/icinga2/modified-attributes.conf Objects path: /var/cache/icinga2/icinga2.debug Vars path: /var/cache/icinga2/icinga2.vars PID path: /run/icinga2/icinga2.pid

Build information: Compiler: GNU 7.3.0 Build host: 10fe80b7e2af

• Operating System and version: System information: Platform: Ubuntu Platform version: 18.04 LTS (Bionic Beaver) Kernel: Linux Kernel version: 4.15.0-22-generic Architecture: x86_64
• Webserver, PHP versions: nginx, php7.1

Can anybody reproduce or is this an issue on my side? Also, where should the user object be saved (and where is director fetching it from?) in case it was successful?

[lazyfrosch]

No I'm sorry ApiUser never was meant to be deployed from Director.

Similar to Zones and Endpoints these should only be used as reference in Director, but not as part of the deployed config.

In particular for ApiUser it only was ever built to store credentials for Director's API handling to Icinga 2.

[Thomas-Gelf]

@lazyfrosch is right here. This might be implemented as a feature one day, but it's not on our priority list.

[tonnenpinguin]

Understood, thanks guys! Might be worth mentioning in the docs/disabling the feature for now to not confuse people.