-
Notifications
You must be signed in to change notification settings - Fork 41
Update existing trigger feeds on create instead of failing #360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
action/lib/Database.js
Outdated
| reject(err); | ||
| if(err.statusCode && err.statusCode === 409) { | ||
| this.getTrigger(params.triggerName) | ||
| .then(() => this.disableTrigger(params.triggerName)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why all this async stuff is going on when the entire action functionality is blocking anyway...
|
@jasonpet, will definitely need your Node.js expertise on this one. |
d8a183b to
c87016d
Compare
4aff3cc to
4634bc1
Compare
jasonpet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If for some reason a trigger is deleted, but the corresponding feed is not, allow a trigger in the same namespace with the same trigger name to be recreated with the existing feed.