Apply docs changes from #3446 to master #3525
Merged
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
adds reference to private beta in order to ensure use env var correctly
|
Note to self: Remember to cherry-pick this to |
marcotc
approved these changes
Mar 14, 2024
|
Thanks Marco for the review! I've gone ahead and pushed this to the (And since I pushed the exact hash that's in master, it won't cause conflicts for next version :D) |
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?
This PR brings the changes from #3446 that were directly applied to our docs ("release" branch) into the master branch.
Motivation:
This makes sure the changes don't get lost during the release process.
Additional Notes:
N/A
How to test the change?
Check diff looks good :)
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance.