Skip to content

additional alarm configuration for each stack #94

@GwonsooLee

Description

@GwonsooLee

For each stack, slack alarm configuration is needed because some of stacks are really critical to the service so that failure deployment should be alarm in a special way.

Currently, goployer sends the process of deployment with slack message but this is not enough to check failure if it is timeout failure ( timeout is , by default, 1 hour )

I think only two more configurations needed for this feature

stack:
  slack_url: 
  notification_level: failure / all 

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is needed

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions