consul/website/source/docs/connect/proxies
Matt Keeler acfd87c673
Improve Connect with Prepared Queries (#5291)
Given a query like:

```
{
   "Name": "tagged-connect-query",
   "Service": {
      "Service": "foo",
      "Tags": ["tag"],
      "Connect": true
   }
}
```

And a Consul configuration like:

```
{
   "services": [
      "name": "foo",
      "port": 8080,
      "connect": { "sidecar_service": {} },
      "tags": ["tag"]
   ]
}
```

If you executed the query it would always turn up with 0 results. This was because the sidecar service was being created without any tags. You could instead make your config look like:

```
{
   "services": [
      "name": "foo",
      "port": 8080,
      "connect": { "sidecar_service": {
         "tags": ["tag"]
      } },
      "tags": ["tag"]
   ]
}
```

However that is a bit redundant for most cases. This PR ensures that the tags and service meta of the parent service get copied to the sidecar service. If there are any tags or service meta set in the sidecar service definition then this copying does not take place. After the changes, the query will now return the expected results.

A second change was made to prepared queries in this PR which is to allow filtering on ServiceMeta just like we allow for filtering on NodeMeta.
2019-02-04 09:36:51 -05:00
..
envoy.md Invalid syntax in Envoy configuration docs. (#5275) 2019-01-28 09:58:29 -05:00
integrate.html.md [WIP] Initial draft of Sidecar Service and Managed Proxy deprecation docs (#4752) 2018-10-11 10:44:42 +01:00
managed-deprecated.html.md Fix some broken links in docs (#4858) 2018-10-26 10:55:12 -07:00
sidecar-service.md Improve Connect with Prepared Queries (#5291) 2019-02-04 09:36:51 -05:00