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

Fix environment end-point links to be compatible with our docs site #955

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions documentation/api/query/v4/environments.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@ canonical: "/puppetdb/latest/api/query/v4/environments.html"

[curl]: ../curl.html#using-curl-from-localhost-non-sslhttp
[paging]: ./paging.html
[events]: ./events.html
[reports]: ./reports.html
[resources]: ./resources.html
[facts]: ./facts.html

Environments can be queried by making an HTTP request to the `/environments` REST
endpoint.
Expand Down Expand Up @@ -64,12 +68,12 @@ The response is a JSON hash of the form:
### `GET /v4/environments/<ENVIRONMENT>/[events|facts|reports|resources]`

These routes are identical to issuing a request to
'/v4/[events|facts|reports|resources]', with a query parameter of
["=" "environment" "<ENVIRONMENT>"]. All query parameters and route
`/v4/[events|facts|reports|resources]`, with a query parameter of
`["=","environment","<ENVIRONMENT>"]`. All query parameters and route
suffixes from the original routes are supported. The result format is also
the same. Additional query parameters are ANDed with the environment
clause. See [/v4/events](./events.html), [/v4/facts](./facts.html),
[/v4/reports](./reports.html) or [/v4/resources](./resources.html) for
clause. See [/v4/events][events], [/v4/facts][facts],
[/v4/reports][reports] or [/v4/resources][resources] for
more info.

## Paging
Expand Down
2 changes: 1 addition & 1 deletion documentation/puppetdb-faq.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ agent runs, the amount of changes to the nodes on each run etc. One
possible cause of execessive load on the database server is a low
catalog duplication rate. See the [PuppetDB dashboard][maintaining_tuning]
to find this rate for your PuppetDB instance. If this rate is
significantly lower than 90%, see [Why is my catalog duplication rate so low?][#why-is-my-catalog-duplication-rate-so-low].
significantly lower than 90%, see [Why is my catalog duplication rate so low?](#why-is-my-catalog-duplication-rate-so-low).

## Why is my catalog duplication rate so low?

Expand Down