Skip to content
This repository has been archived by the owner on Oct 24, 2019. It is now read-only.

CloudFormation parameter updates #98

Closed
k-mahoney opened this issue Nov 6, 2017 · 3 comments
Closed

CloudFormation parameter updates #98

k-mahoney opened this issue Nov 6, 2017 · 3 comments
Assignees

Comments

@k-mahoney
Copy link
Contributor

Currently the GitHub repository dispatch tickets are opened in is set via the CloudFormation template. This should be updated such that the repository specified in the template acts as the default or fallback destination for dispatch tickets and allow a repository to be specified in the message specification. This way different dispatch alerts can be ticketed in specific repositories, rather than all defaulting to one.

/cc @alulsh

@alulsh alulsh mentioned this issue Nov 6, 2017
7 tasks
@alulsh
Copy link
Member

alulsh commented Nov 7, 2017

We'll also need to add a CloudFormation parameter for the fallback GitHub team, right now this is hard coded to @mapbox/security in https://github.com/mapbox/dispatch/blob/master/incoming/function.js#L113.

@alulsh
Copy link
Member

alulsh commented Nov 7, 2017

@k-mahoney is going to work on both of these today.

@k-mahoney
Copy link
Contributor Author

Complete in #104

@k-mahoney k-mahoney added this to Complete in Dispatch Roadmap Nov 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants