Skip to content
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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

dgreen15
Copy link
Contributor

@dgreen15 dgreen15 commented Jul 17, 2024

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

  • [ x] Please merge after reviewing

Additional notes

@github-actions github-actions bot added the Images Images are added/removed with this PR label Jul 17, 2024
@dgreen15 dgreen15 marked this pull request as ready for review July 17, 2024 18:03
@dgreen15 dgreen15 requested a review from a team as a code owner July 17, 2024 18:03
Copy link
Contributor

github-actions bot commented Jul 17, 2024

@drichards-87
Copy link
Contributor

Created DOCS-8475 for Docs Team review.

@drichards-87 drichards-87 added the editorial review Waiting on a more in-depth review label Jul 17, 2024
Copy link
Contributor

@domalessi domalessi left a 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
Copy link
Contributor

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


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.
Copy link
Contributor

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.

Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

dgreen15 and others added 2 commits July 23, 2024 17:07
Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial review Waiting on a more in-depth review Images Images are added/removed with this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants