-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[DOCS-10475] Rename Google Chronicle to Google SecOps #28465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
urseberry
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for the review guidance!
| @@ -1 +1 @@ | |||
| Enter the Google Chronicle endpoint URL. For example, `https://chronicle.googleapis.com`. No newline at end of file | |||
| Enter the Google SecOps endpoint URL. For example, `https://chronicle.googleapis.com`. No newline at end of file | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, Google hasn't changed the endpoint URL yet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for reviewing @urseberry! They haven't: https://cloud.google.com/chronicle/docs/reference/rest#service-endpoint. They also haven't updated their docs url: https://cloud.google.com/chronicle/docs) 😄
|
Closed in favor of: #33655 |
What does this PR do? What is the motivation?
Google ChronicletoGoogle SecOpsfor OP docs.For docs reviewer:
There's no need to go through all the files because it was mostly a find and replace update. Could you just check these files and the staging previews for them?
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes