Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/415
@dlyle65535 I think that's a great point and thanks for clarifying.
Looking at that file, it appears that ambari is explicitly providing the
ability to modify the global config and certain flux topology properties files,
but not a screen to manage the sensor-specific configuration content (i.e. at
present parsers and enrichment). Please correct if I have had a reading
comprehension SNAFU ;) If so, since we just added a new set of configs under
the same config directory and provided hooks for `zk_load_utils.sh` to know how
to load and get them, it shouldn't be any different than the existing configs.
That being said, it is a good point you make. Let me restate it and you
tell me if I have the gist. If people change the configs on an m-pack
installed cluster via the CLI (via `zk_load_utils.sh`) or the
soon-to-be-committed management UI, ambari will revert those changes on service
restart, correct?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
