What happened:
As part of the demo/testing we used a stand alone alert in AlertsConfig and it created WavefrontAlert. The expectation is it should error out if a WavefrontAlert doesn't have any exportedParam fields otherwise its just a duplicate since there are no changes from original WavefrontAlert which was already created as part of Standalone Wavefront Alert.
What you expected to happen:
It should error out with stating that there is no exportParams field in the WavefrontAlert.
How to reproduce it (as minimally and precisely as possible):
Create Wavefront stand alone alert
Use that in one of the AlertsConfig
This will have 2 alerts in wavefront without any changes(duplicates)
Is this a BUG REPORT or FEATURE REQUEST?: Bug
What happened: As part of the demo/testing we used a stand alone alert in AlertsConfig and it created WavefrontAlert. The expectation is it should error out if a WavefrontAlert doesn't have any exportedParam fields otherwise its just a duplicate since there are no changes from original WavefrontAlert which was already created as part of Standalone Wavefront Alert.
What you expected to happen: It should error out with stating that there is no exportParams field in the WavefrontAlert.
How to reproduce it (as minimally and precisely as possible):
This will have 2 alerts in wavefront without any changes(duplicates)
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs