-
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
Update adding_metadata.md #24196
base: master
Are you sure you want to change the base?
Update adding_metadata.md #24196
Conversation
Preview links (active after the
|
Created DOCS-8475 for Docs Team review. |
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 putting this up, @dgreen15 ! Left some comments. Give them a look and let me know if you have any questions!
|
||
[17]: http://json-schema.org/ | ||
[18]: https://www.schemastore.org/json/ | ||
[19]: https://raw.githubusercontent.com/DataDog/schema/main/service-catalog/version.schema.json |
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.
This link seems to be broken? I'm getting a 404.
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.
Is this the right link: https://github.com/DataDog/schema/blob/main/service-catalog/service.schema.json ??
|
||
Datadog provides a [JSON Schema][17] for service definitions so that when you are editing a service definition in a [supporting IDE][18], features such as autocomplete and validation are provided. The [JSON schema for Datadog service definitions][19] is registered with the open source [Schema Store][18]. | ||
|
||
The plugin supports the new v3.0 schema and includes information that will tell your IDEs which filenames it applies to—specifically, the files entity.datadog.yaml, entity.datadog.yml, and entity.datadog.json to quickly and accurately complete your entity definition file without referencing documentation. In the example below, the IDE automatically creates keys as you fill out the entity definition. |
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.
We say "plugin" here (and "plugin" is in the title as well), but it's unclear to me what exactly this refers to. Is the Datadog JSON Schema a plugin? I would suggest using plugin everywhere or using some other word like "integration". Whatever you think is best, and just stay consistent.
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.
Also, I'm not sure how much value-add it is to include "supports the new v3.0 schema"? If you do think this is important, then I'd ask you to clarify what this refers to -- is v3.0 the version for JSON Schema or for Datadog's JSON Schemas? (Let me know if my question doesn't make sense.)
|
||
Datadog provides a [JSON Schema][17] for service definitions so that when you are editing a service definition in a [supporting IDE][18], features such as autocomplete and validation are provided. The [JSON schema for Datadog service definitions][19] is registered with the open source [Schema Store][18]. | ||
|
||
The plugin supports the new v3.0 schema and includes information that will tell your IDEs which filenames it applies to—specifically, the files entity.datadog.yaml, entity.datadog.yml, and entity.datadog.json to quickly and accurately complete your entity definition file without referencing documentation. In the example below, the IDE automatically creates keys as you fill out the entity definition. |
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.
The plugin supports the new v3.0 schema and includes information that will tell your IDEs which filenames it applies to—specifically, the files entity.datadog.yaml, entity.datadog.yml, and entity.datadog.json to quickly and accurately complete your entity definition file without referencing documentation. In the example below, the IDE automatically creates keys as you fill out the entity definition. | |
The plugin informs your IDE about the applicable files—namely, `entity.datadog.yaml`, `entity.datadog.yml`, and `entity.datadog.json`—so you can complete your entity definition file without referencing documentation. In the following example, the IDE automatically creates keys as you fill out the entity definition. |
Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
What does this PR do? What is the motivation?
Moves a section in service catalog docs and adds a short gif. Replaces image in software templates sub-page. Adds a blog link to software templates sub-page
Merge instructions
Additional notes