status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-11 14:24:39 +00:00
Code Issues Projects Releases Wiki Activity

Typos

Browse Source
This commit is contained in:
Paul Banks 2018-07-13 23:09:34 +01:00
parent dcd157ec7c
commit fa29fee4b6
No known key found for this signature in database
GPG Key ID: C25A851A849B8221
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/docs/connect/native/go.html.md
View File

@ -168,17 +168,17 @@ discovery mechanism for the target. **It's not actually resolved via DNS** but
used as a logical identifier for a Consul service discovery mechanism. It has used as a logical identifier for a Consul service discovery mechanism. It has
the following specific limitations: the following specific limitations:
* The sheme must be `https://`. * The scheme must be `https://`.
* It must be a Consul DNS name in one of the following forms: * It must be a Consul DNS name in one of the following forms:
* `<name>.service[.<datacenter>].consul` to discover a healthy service * `<name>.service[.<datacenter>].consul` to discover a healthy service
instance for a given service. instance for a given service.
* `<name>.query[.<datacenter>].consul` to discover an instance via * `<name>.query[.<datacenter>].consul` to discover an instance via
[Prepared Query](/api/query.html). [Prepared Query](/api/query.html).
* The top-level domain _must_ be `.consul` even if your cluster has a custom * The top-level domain _must_ be `.consul` even if your cluster has a custom
`domain` configured for it's DNS interface. This might be relaxed in the `domain` configured for it's DNS interface. This might be relaxed in the
future. future.
* Tag filters for services are not currently supported (i.e. * Tag filters for services are not currently supported (i.e.
`tag1.web.service.consul`) however the same behaviour can be acheived using a `tag1.web.service.consul`) however the same behaviour can be achieved using a
prepared query. prepared query.
* External DNS names, raw IP addresses and so on will cause an error and should * External DNS names, raw IP addresses and so on will cause an error and should
be fetched using a separate `HTTPClient`. be fetched using a separate `HTTPClient`.