Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@nickwallen WRT Test plan:
Do we have a generic smoke test plan? If so, then I'll reference it. If
not I will spell it out more clearly.
There are, I think two aspects to this that I would like to detangle.
From a 'how metron works' point of view, this change does not change what the
system does in an observable way, it retains the status quo ante functionality.
So that test plan is not different than another change that says "run up in
full dev and verify that that topologies are running etc....". That being
said, I will list it out in more detail. I apologize for the vagueness. The
other point of view, which I think you are referencing is "as a metron
developer, who may have to add a new parser to metron proper". This **is**
different from before, but was also not documented in the old architecture
either, which is why I didn't take a stab at the dev guide in this PR. We also
do not have guides for adding new ambari services, adding components to the
rpm, creating new ambari scripts as well, all things I had to reverse and
figure out to get this working, and we did not hold up those efforts to wait for
them, so I did not think it was required.
That is not to say that I don't agree such things should exist, and maybe
should have been required then and be required now. I will certainly take a
stab at it
---
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.
---
