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

Add developer docs #6623

Merged
merged 24 commits into from
May 15, 2020
Merged

Add developer docs #6623

merged 24 commits into from
May 15, 2020

Conversation

ofek
Copy link
Contributor

@ofek ofek commented May 12, 2020

What does this PR do?

https://datadoghq.dev/integrations-core/

Motivation

Better docs for a better world.

Additional Notes

For implementation details, see https://datadoghq.dev/integrations-core/meta/docs/

@codecov
Copy link

codecov bot commented May 12, 2020

Codecov Report

Merging #6623 into master will increase coverage by 0.57%.
The diff coverage is n/a.

Impacted Files Coverage Δ
disk/tests/common.py 61.53% <0.00%> (-38.47%) ⬇️
disk/tests/conftest.py 85.71% <0.00%> (-11.43%) ⬇️
dns_check/datadog_checks/dns_check/dns_check.py 84.00% <0.00%> (-5.00%) ⬇️
disk/datadog_checks/disk/disk.py 82.80% <0.00%> (-3.61%) ⬇️
disk/tests/test_filter.py 96.45% <0.00%> (-3.55%) ⬇️
...se/datadog_checks/base/utils/metadata/constants.py
riak/datadog_checks/riak/__init__.py
proxysql/datadog_checks/proxysql/__init__.py
tomcat/datadog_checks/tomcat/__init__.py
oracle/tests/test_config.py
... and 529 more

Copy link
Member

@mgarabed mgarabed left a comment

Choose a reason for hiding this comment

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

There is so much great stuff in here 🎉

But it also covers so much ground - it might be helpful to break it down into separate PRs for docs-only, and doc generation code ..

README.md Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/checks/base.py Outdated Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/checks/base.py Outdated Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/checks/base.py Outdated Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/checks/base.py Outdated Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/utils/db/core.py Outdated Show resolved Hide resolved
datadog_checks_base/datadog_checks/base/utils/db/query.py Outdated Show resolved Hide resolved
datadog_checks_dev/datadog_checks/dev/docker.py Outdated Show resolved Hide resolved
datadog_checks_dev/datadog_checks/dev/docker.py Outdated Show resolved Hide resolved
datadog_checks_dev/datadog_checks/dev/terraform.py Outdated Show resolved Hide resolved
docs/developer/base/databases.md Outdated Show resolved Hide resolved
ofek and others added 3 commits May 14, 2020 09:55
Co-Authored-By: Julia <[email protected]>
* Add SNMP documentation

* Address formatting feedback

* Document metric types, explain how to recognize symbol metrics

* Add note on choosing tag sources

* Fix explanation about index tags

* Address nits
Copy link
Contributor

@florimondmanca florimondmanca left a comment

Choose a reason for hiding this comment

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

Congratulations on this humongous bag of work :)

As Mike said there's a lot of great stuff and new stuff in this. Definitely going to be helpful. (But tbh, wondering how long until a substantial part of this becomes outdated, he! IMO we should aim for a wiki-like edit experience, and the auto-deploy-on-push-edit workflow will definitely help there.)

Holding off onto my ✅ because I have a few nits and questions, but this LGTM.

Comment on lines +72 to +74
result = run_or_abort(
f'git commit -m "build docs at {latest_commit_hash}"', capture=True, ignore_exit_code=True
)
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a heads up FYI: I have my git setup to commit with my DD account and GPG keys inside ~/dd, and my personal account (and keys) elsewhere, and this command makes git use my personal account.

I'm not sure why. Obviously we're not inside ~/dd at this point (but in a random tmp dir), but the git config setup done above should override my ~/.gitconfig-*, right? I also tried passing git commit --author "{git_user} <{git_email}>" but it doesn't take it into account either.

Not a big issue but if you have any clues I'd be interested. :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm that's interesting. I'm not sure

docs/developer/base/http.md Outdated Show resolved Hide resolved
docs/developer/meta/config-specs.md Outdated Show resolved Hide resolved
Copy link
Contributor

@florimondmanca florimondmanca left a comment

Choose a reason for hiding this comment

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

New browser opening in docs serve works fab 💯

LGTM

Copy link
Member

@mgarabed mgarabed left a comment

Choose a reason for hiding this comment

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

🔥 * 💯 !

Copy link
Contributor

@ChristineTChen ChristineTChen left a comment

Choose a reason for hiding this comment

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

🏅

@ofek ofek merged commit a58781f into master May 15, 2020
@ofek ofek deleted the hack-a-doc branch May 15, 2020 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants