-
Notifications
You must be signed in to change notification settings - Fork 0
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
API Usage Chart Repair #85
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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, but is the logic right? Maybe I don't understand
{ | ||
/* If we're specifying a USAGE_ID then we definitely don't want to | ||
be creating API keys in that AWS environment! */ | ||
isApiManagerEnabled() && USAGE_ID === null && ( |
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.
Should this be enabling account creation when USAGE_ID is null? Shouldn't it be the opposite?
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.
If USAGE_ID is set, then we don't have full access to the AWS instance, so probably shouldn't be creating AWS users and keys! If it is UNset, then we are safe to do so
Corrects some assumptions made during the development of these graphs. Most notable is a new
USAGE_ID
filter which lets you only show graphs and stats from a certain usage id.