[synthetics] adding the documentation for the resourceUrlSubstitutionRegexes #27722
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
Preview links (active after the
|
etnbrd
force-pushed
the
etnbrd/SYNTH-18457/resourceUrlSubstitionRegex
branch
2 times, most recently
from
7d5a5c6 to
582fdde
Compare
etnbrd
force-pushed
the
etnbrd/SYNTH-18457/resourceUrlSubstitionRegex
branch
from
582fdde to
e3bca52
Compare
etnbrd
changed the title
|
Created DOCS-10178 for in-depth review. |
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.
What does this PR do? What is the motivation?
This PR adds the documentation for the new
resourceUrlSubstitutionRegexesfeature which we deployed in production just now. And it contextualise a bit the rest of the pages to accommodate this addition.Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/descriptionnaming convention) and then add the following PR comment:Additional notes