Add PERF_INGEST_TOKEN Requirement To Post Perf Data to DB - #55
Closed
micah-wil wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Micah Williamson <micah.williamson@amd.com>
Collaborator
Author
|
Handled in a different PR |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authenticate so only the official BK pipeline (which holds the shared secret) can post to the perf dashboard's ingestion endpoint. Off-pipeline runs without the token get rejected by the ingest service. Ingestion is best-effort so any runs that get rejected due to lack of a valid token will still continue to run to completion.