Enhancement: Allowing alarms to be disabled in stages

[malachi-constant]

Enhancement

• Adds ability to disable cloudwatch alarms in DataStages by setting alarm_threshold value to 0
• Adds test using the above setting

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[LeonLuttenberger]

Just an idea, but I wonder if it would be better to just have a standard alarms_enabled parameter that's define in Stage, and is therefore inherited by all the stages.

I'm just thinking it might be easier if all the stages have the same parameter which can be used to disable the alarm, as opposed to each stage having it be a different name.

[malachi-constant]

Just an idea, but I wonder if it would be better to just have a standard alarms_enabled parameter that's define in Stage, and is therefore inherited by all the stages.

I'm just thinking it might be easier if all the stages have the same parameter which can be used to disable the alarm, as opposed to each stage having it be a different name.

Yep that's kind of what I was thinking with the alarm_threshold=0 behavior but it having its own explicit parameter would be best. The only drawback I can see with that is future cases could involve multiple alarms where the user might want to be selective about what is created.