Update systemlink-secretys.yaml for testmonitoreventprocessor-apikey#316
Merged
BKnight760 merged 1 commit intoni:mainfrom Feb 24, 2026
Merged
Update systemlink-secretys.yaml for testmonitoreventprocessor-apikey#316BKnight760 merged 1 commit intoni:mainfrom
BKnight760 merged 1 commit intoni:mainfrom
Conversation
aaron-ni
requested review from
BKnight760,
CIakab-NI,
JD-Robertson,
WillCawley and
prestwick
as code owners
Contributor
Author
|
This is essentially the same as #292, but for Test Monitor Service. |
JD-Robertson
approved these changes
Jan 28, 2026
CIakab-NI
approved these changes
Feb 24, 2026
BKnight760
approved these changes
Feb 24, 2026
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
5 participants
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.
CONTRIBUTING.md.
What does this Pull Request accomplish?
Add initialization for
testmonitoreventprocessor-apikey. The test monitor event processor (currently in development) needs an API key to authorize background requests to the routine service.Why should this Pull Request be merged?
Updates
getting-startedmaterials for new feature.What testing has been done?
Testing for new API keys on internal deployments/PRs.