Skip to content

Conversation

@j0k3r
Copy link
Contributor

@j0k3r j0k3r commented Feb 8, 2019

The way validateConfig works will generate some error logs when no alarms are defined at all.

After upgrading to the latest serverless-step-functions we got some logs about alarms but we don't have alarms defined. I think we should not have log about "alarms config is malformed" when no alarms are defined.

Following #167

Sidenote: I've enable sinon.spy() instead of console.log in compileIamRole.test.js to avoid noisy log during tests. I can remove that if you don't agree.

The way `validateConfig` works will generate some error logs when no
alamrs are defined at all.

After upgrading to the latest serverless-step-functions we got some logs
about alarms but we don't have alarms defined.

I think we should not have log about "alarms config is malformed" when
no alarms are defined.
Copy link
Collaborator

@theburningmonk theburningmonk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@theburningmonk theburningmonk merged commit 696635f into serverless-operations:master Feb 8, 2019
@j0k3r j0k3r deleted the fix/avoid-log-no-alarms branch February 8, 2019 12:23
@theburningmonk
Copy link
Collaborator

This has been deployed as part of 1.12.1

ss-betseqnzr pushed a commit to BetSEQNZR/serverless-step-functions that referenced this pull request Sep 8, 2023
…-no-alarms

Avoid alarms logs when no alarms are defined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants