-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(gorgone): when pushing engine conf, push centreon_vmware daemon configuration #1718
base: develop
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
063aae4
to
1bdc8f9
Compare
3eeadac
to
37c1df4
Compare
a386a1a
to
34b9492
Compare
Refs:MON-144643
Refs:MON-144643
Refs:MON-144643
When gorgone receive a message to push the engine configuration (from the centcore file directory) gorgone now also push the centreon_vmware.json file in /etc/centreon/ for the centreon_vmware daemon and restart the daemon while restarting engine. As centreon_vmware don't support reload, when engine reload we restart centreon_vmware. Refs:MON-144643
Add the list of column to insert data into. Refs:MON-144643
Check gorgone retrieve data from the /var/lib/centreon/centcore/ directory, and send the forced check to the engine pipe. We use a perl script to mock the pipe, as we don't want to run engine, and gorgone check the file is a real pipe and not a simple file. Check gorgone push engine, broken and vmware configuration files to the poller, and the poller set the correct path. Gorgone don't seem to correctly take the configuration modules:engine:command_file. The default /var/lib/centreon-engine/rw/centengine.cmd is used instead, this should be investigated in a separate ticket. gorgone don't set user/group when processing folder with untar. create centcore folder in each tests As www-data don't exist on rpm based distro, we can't test if user/group is correctly set by gorgone. Refs:MON-144643
…ests and update statistic tests to use new version of databaseLibrary. Refs:MON-144643
1160f10
to
4c2ef54
Compare
This should be enabled back by the next ticket. Refs:MON-144643
Description
As we want vault support, the centreon_vmware daemon configuration now have to be managed by the central.
This PR aim to push a centreon_vmware.json conf file to each poller with the vmware authentication configured by the user in the webapp.
This file can contain vault path instead of clear text password, to be decided by the webapp when exporting the conf.
Another ticket aim to upgrade the centreon_vmware daemon to read this file.
Fixes # MON-144643
Type of change
Target serie
How this pull request can be tested ?
Add an ACC for vmware in the webapp for a poller.
Export the configuration to this poller from the webapplication.
Check on the poller the file /etc/centreon/centreon_vmware.json exist, and contain the correct data configured in the webapp.
Checklist