-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix Push API Key validation in diagnose report (#416)
The Push API key validation wasn't implemented previously. I've now implemented a validation by calling the AppSignal.com auth endpoint with the configured Push API key. The http(s) library doesn't a way to make synchronous requests that I could find, so I had to update the diagnose tool and script to be async, by using the async and await keywords all the way up the chain of functions. The rest of the implementation such as the coloring of the output, and storing of the result on the report, was already implemented. I've updated the diagnose tests submodule to account for this change in behavior in the tests. Fix #408
- Loading branch information
Showing
5 changed files
with
58 additions
and
21 deletions.
There are no files selected for viewing
5 changes: 5 additions & 0 deletions
5
packages/nodejs/.changesets/validate-push-api-key-in-diagnose-report.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
bump: "patch" | ||
--- | ||
|
||
Fix the validation of Push API key in the diagnose report. It would always print "valid" even if the key was not set or invalid. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters