Updated grafana request to include custom data per target. - DO NOT MERGE - Awaiting Grafana update #233
Conversation
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
Removed mapping from Stage as no required. Moved `Access-Control-Allow-Credentials` header setting to middleware Added or logic on optional stage in custom data from grafana request to allow rollout with new and legacy support.
phillipbarron
requested review from
a team,
twrichards and
aracho1
as code owners
phillipbarron
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removed mapping from Stage as no required.
Moved
Access-Control-Allow-Credentialsheader setting to middleware Added or logic on optional stage in custom data from grafana request to allow rollout with new and legacy support.What does this change?
How to test
How can we measure success?
Have we considered potential risks?
Images
Accessibility