-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
API Catalog -> Service Catalog Migration #26763
base: master
Are you sure you want to change the base?
Conversation
* removing deprecation message * proposed changes * Fix typo. --------- Co-authored-by: Brett Blue <[email protected]>
@@ -189,7 +189,7 @@ This table shows the mapping between the metric origin as seen in the facet and | |||
|
|||
| Metric Origin | Submitted from | | |||
| ------------------------| ----------------------------------------------------------------------------- | | |||
| API Catalog | Timeseries sent by the Datadog [API Catalog][13] product from the APIM Endpoint. | |||
| API Catalog | Timeseries sent by the Datadog [Service Catalog][13] product from the APIM Endpoint. |
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.
@ddOfir - Note that this is still the text in Demo for the facet:
@brett0000FF Finished my initial review! Calling out that there's some inconsistency re: using API list vs Endpoint list vs Endpoints list, and bolding vs not bolding the term "Endpoint/s". Also made a few suggestions here and there while I was at it (I know a lot of the work was copy/paste but figured I'd correct glaring things if I could). Otherwise, all looks good! |
Co-authored-by: domalessi <[email protected]>
…on into brett.blue/DOCS-9666
What does this PR do? What is the motivation?
Integrate API Catalog docs into Service Catalog to reflect the new state of the product.
Preview
To do
Consolidate/remove content for API Catalog that's already covered by Service Catalog:
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>/description
naming convention) and then add the following PR comment:Additional notes