status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Clean up additional refs to partition exports

This commit is contained in:
freddygv 2021-12-04 15:16:15 -07:00
parent cacfa79fc2
commit e91509383f
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
agent/consul/config_endpoint.go
View File

@ -594,7 +594,7 @@ func (c *ConfigEntry) ResolveServiceConfig(args *structs.ServiceConfigRequest, r
}
func gateWriteToSecondary(targetDC, localDC, primaryDC, kind string) error {
// Partition exports are gated from interactions from secondary DCs
// ExportedServices entries are gated from interactions from secondary DCs
// because non-default partitions cannot be created in secondaries
// and services cannot be exported to another datacenter.
if kind != structs.ExportedServices {

2
agent/consul/config_replication.go
View File

@ -92,7 +92,7 @@ func (s *Server) reconcileLocalConfig(ctx context.Context, configs []structs.Con
defer ticker.Stop()
for i, entry := range configs {
// Partition exports only apply to the primary datacenter.
// Exported services only apply to the primary datacenter.
if entry.GetKind() == structs.ExportedServices {
continue
}

8
website/content/docs/connect/config-entries/exported-services.mdx
View File

@ -1,12 +1,12 @@
---
layout: docs
page_title: 'Configuration Entry Kind: Partition Exports'
page_title: 'Configuration Entry Kind: Exported Services'
description: >-
The exported-services configuration entry enables you to export services from a single file.
Settings in this configuration entry can apply to services in any namespace of the specified partition. Write access to the mesh resource is required.
---
# Partition Exports
# Exported Services
This topic describes the `exported-services` configuration entry type. The `exported-services` configuration entry enables Consul to export service instances to other admin partitions from a single file. This enables your services to be networked across admin partitions. See [Admin Partitions](/docs/enterprise/admin-partitions) for additional information.
@ -21,7 +21,7 @@ You can configure the settings defined in the `exported-services` configuration
## Requirements
* A Consul Enterprise binary
* A partition that corresponds to the configuration entry. As in, the partition exports config entry for partition "frontend" requires that the "frontend" partition exists
* A partition that corresponds to the configuration entry. As in, the exported services config entry for partition "frontend" requires that the "frontend" partition exists
## Usage
@ -36,7 +36,7 @@ You can configure the settings defined in the `exported-services` configuration
Configure the following parameters to define a `exported-services` configuration entry:
<CodeTabs heading="Partition exports configuration syntax" tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
<CodeTabs heading="Exported services configuration syntax" tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
<CodeBlockConfig>
```hcl

2
website/data/docs-nav-data.json
View File

@ -151,7 +151,7 @@
"path": "connect/config-entries/mesh"
},
{
"title": "Partition Exports",
"title": "Exported Services",
"path": "connect/config-entries/exported-services"
},
{