luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: fix an assortment of broken links

This commit is contained in:
Jack Pearkes 2018-06-25 12:05:29 -07:00
parent 3127fccec4
commit d3cec142d4
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/api/connect/ca.html.md
View File

@ -14,7 +14,7 @@ Certificate Authority mechanism.
## List CA Root Certificates
This endpoint returns the current list of trusted CA root certificates in
This endpoint returns the current list of trusted CA root certificates in
the cluster.
| Method | Path | Produces |
@ -104,7 +104,7 @@ $ curl \
This endpoint updates the configuration for the CA. If this results in a
new root certificate being used, the [Root Rotation]
(/docs/guides/connect-ca.html#rotation) process will be triggered.
(/docs/connect/ca.html#root-certificate-rotation) process will be triggered.
| Method | Path | Produces |
| ------ | ---------------------------- | -------------------------- |

4
website/source/docs/commands/connect/ca.html.md.erb
View File

@ -13,7 +13,7 @@ Command: `consul connect ca`
The CA connect command is used to interact with Consul Connect's Certificate Authority
subsystem. The command can be used to view or modify the current CA configuration. See the
[Connect CA Guide](/docs/guides/connect-ca.html) for more information.
[Connect CA documentation](/docs/connect/ca.html) for more information.
```text
Usage: consul connect ca <subcommand> [options] [args]
@ -64,7 +64,7 @@ The output looks like this:
## set-config
Modifies the current CA configuration. If this results in a new root certificate
being used, the [Root Rotation](/docs/guides/connect-ca.html#rotation) process
being used, the [Root Rotation](/docs/connect/ca.html#root-certificate-rotation) process
will be triggered.
Usage: `consul connect ca set-config [options]`

2
website/source/docs/connect/ca.html.md
View File

@ -33,7 +33,7 @@ will generate the initial root certificates and setup the internal Consul server
state.
For the initial bootstrap, the CA provider can be configured through the
[Agent configuration](docs/agent/options.html#connect_ca_config). After
[Agent configuration](/docs/agent/options.html#connect_ca_config). After
initialization, the CA can only be updated through the
[Update CA Configuration API endpoint](/api/connect/ca.html#update-ca-configuration).
If a CA is already initialized, any changes to the CA configuration in the

2
website/source/docs/connect/ca/consul.html.md
View File

@ -82,7 +82,7 @@ been generated (as seen above in the roots list).
There are two ways to have the Consul CA use a custom private key and root certificate:
either through the `ca_config` section of the [Agent configuration]
(docs/agent/options.html#connect_ca_config) (which can only be used during the cluster's
(/docs/agent/options.html#connect_ca_config) (which can only be used during the cluster's
initial bootstrap) or through the [Update CA Configuration endpoint]
(/api/connect/ca.html#update-ca-configuration).

2
website/source/docs/connect/intentions.html.md
View File

@ -117,7 +117,7 @@ Consul supporting namespaces.
## Intention Management Permissions
Intention management can be protected by [ACLs](/docs/guides/acls.html).
Intention management can be protected by [ACLs](/docs/guides/acl.html).
Permissions for intentions are _destination-oriented_, meaning the ACLs
for managing intentions are looked up based on the destination value
of the intention, not the source.