Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

Check for GITHUB_ACCESS_TOKEN in env #152

Closed
trescube opened this issue Mar 13, 2018 · 0 comments
Closed

Check for GITHUB_ACCESS_TOKEN in env #152

trescube opened this issue Mar 13, 2018 · 0 comments
Labels
/maintainers /submit v1

Comments

@trescube
Copy link
Member

Currently the process.env settings are checked for here.

Since the endpoints run as lambdas, it makes more sense for the routes that depend on the values to check for them as preconditions and return HTTP 500 if the values aren't there.
@trescube trescube changed the title Move env settings checks to individual endpoints Check for GITHUB_ACCESS_TOKEN in env Mar 14, 2018
@trescube trescube mentioned this issue Mar 14, 2018
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
/maintainers /submit v1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@trescube