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.

Sign up for GitHub

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

Jump to bottom

Show email configuration on the configuration on demand #1401

Closed
juankaromo opened this issue Apr 22, 2019 · 2 comments
Closed

Show email configuration on the configuration on demand #1401

juankaromo opened this issue Apr 22, 2019 · 2 comments
Assignees
@juankaromo
Labels
type/bug Bug issue
Milestone
17th week sprint

Comments

@juankaromo
Copy link
Contributor

juankaromo commented Apr 22, 2019 •
edited
Loading

Hi team,

Some email configuration fields are not showing up in our config on-demand global section. We need to append the output of /manager/config/mail/global to the output of the current call /manager/config/analysis/global. Remember to take into account a cluster vs. a non-cluster configuration.

Regards.
@juankaromo juankaromo added the type/bug Bug issue label Apr 22, 2019
@juankaromo juankaromo added this to the 17th week sprint milestone Apr 22, 2019
@juankaromo juankaromo self-assigned this Apr 22, 2019
@juankaromo
Copy link
Contributor Author

Working on this branch https://github.com/wazuh/wazuh-kibana-app/tree/mail-config

@juankaromo
Copy link
Contributor Author

juankaromo commented Apr 22, 2019 •
edited
Loading

Update

A new call is made to /manager/config/mail/global to get the missing mail configuration. They were taking this configuration from the output of /manager/config/analysis/global, in which they didn't exist.

@juankaromo juankaromo mentioned this issue Apr 22, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juankaromo juankaromo

Labels
type/bug Bug issue
Projects
None yet
Milestone
17th week sprint
Development

No branches or pull requests
2 participants
@jesusgn90 @juankaromo