-
Notifications
You must be signed in to change notification settings - Fork 59
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
camelcase dispplay-name & sub-category
Signed-off-by: ayush_gitk <ayushsharmaa101@gmail.com>
- Loading branch information
Showing
52 changed files
with
54 additions
and
54 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
templates/meshmodel/components/v1.0.2/exportedservices.meshery.layer5.io_meshmodel.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
{"kind":"ExportedServices","apiVersion":"consul.hashicorp.com/v1alpha1","display-name":"Exported Services","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","display-name":"CONSUL","category":"Orchestration \u0026 Management","sub-category":"Service Mesh"},"schema":"{\n \"description\": \"ExportedServicesSpec defines the desired state of ExportedServices.\",\n \"properties\": {\n \"services\": {\n \"description\": \"Services is a list of services to be exported and the list of partitions to expose them to.\",\n \"items\": {\n \"description\": \"ExportedService manages the exporting of a service in the local partition to other partitions.\",\n \"properties\": {\n \"consumers\": {\n \"description\": \"Consumers is a list of downstream consumers of the service to be exported.\",\n \"items\": {\n \"description\": \"ServiceConsumer represents a downstream consumer of the service to be exported.\",\n \"properties\": {\n \"partition\": {\n \"description\": \"Partition is the admin partition to export the service to.\",\n \"type\": \"string\"\n },\n \"peer\": {\n \"description\": \"[Experimental] Peer is the name of the peer to export the service to.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"type\": \"array\"\n },\n \"name\": {\n \"description\": \"Name is the name of the service to be exported.\",\n \"type\": \"string\"\n },\n \"namespace\": {\n \"description\": \"Namespace is the namespace to export the service from.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"type\": \"array\"\n }\n },\n \"title\": \"Exported Services\",\n \"type\": \"object\"\n}"} | ||
{"kind":"ExportedServices","apiVersion":"consul.hashicorp.com/v1alpha1","displayName":"Exported Services","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","displayName":"CONSUL","category":"Orchestration \u0026 Management","subCategory":"Service Mesh"},"schema":"{\n \"description\": \"ExportedServicesSpec defines the desired state of ExportedServices.\",\n \"properties\": {\n \"services\": {\n \"description\": \"Services is a list of services to be exported and the list of partitions to expose them to.\",\n \"items\": {\n \"description\": \"ExportedService manages the exporting of a service in the local partition to other partitions.\",\n \"properties\": {\n \"consumers\": {\n \"description\": \"Consumers is a list of downstream consumers of the service to be exported.\",\n \"items\": {\n \"description\": \"ServiceConsumer represents a downstream consumer of the service to be exported.\",\n \"properties\": {\n \"partition\": {\n \"description\": \"Partition is the admin partition to export the service to.\",\n \"type\": \"string\"\n },\n \"peer\": {\n \"description\": \"[Experimental] Peer is the name of the peer to export the service to.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"type\": \"array\"\n },\n \"name\": {\n \"description\": \"Name is the name of the service to be exported.\",\n \"type\": \"string\"\n },\n \"namespace\": {\n \"description\": \"Namespace is the namespace to export the service from.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"type\": \"array\"\n }\n },\n \"title\": \"Exported Services\",\n \"type\": \"object\"\n}"} |
2 changes: 1 addition & 1 deletion
2
templates/meshmodel/components/v1.0.2/ingressgateway.meshery.layer5.io_meshmodel.json
Large diffs are not rendered by default.
Oops, something went wrong.
2 changes: 1 addition & 1 deletion
2
templates/meshmodel/components/v1.0.2/mesh.meshery.layer5.io_meshmodel.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
{"kind":"Mesh","apiVersion":"consul.hashicorp.com/v1alpha1","display-name":"Mesh","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","display-name":"CONSUL","category":"Orchestration \u0026 Management","sub-category":"Service Mesh"},"schema":"{\n \"description\": \"MeshSpec defines the desired state of Mesh.\",\n \"properties\": {\n \"http\": {\n \"description\": \"HTTP defines the HTTP configuration for the service mesh.\",\n \"properties\": {\n \"sanitizeXForwardedClientCert\": {\n \"type\": \"boolean\"\n }\n },\n \"required\": [\n \"sanitizeXForwardedClientCert\"\n ],\n \"type\": \"object\"\n },\n \"peering\": {\n \"description\": \"Peering defines the peering configuration for the service mesh.\",\n \"properties\": {\n \"peerThroughMeshGateways\": {\n \"description\": \"PeerThroughMeshGateways determines whether peering traffic between control planes should flow through mesh gateways. If enabled, Consul servers will advertise mesh gateway addresses as their own. Additionally, mesh gateways will configure themselves to expose the local servers using a peering-specific SNI.\",\n \"type\": \"boolean\"\n }\n },\n \"type\": \"object\"\n },\n \"tls\": {\n \"description\": \"TLS defines the TLS configuration for the service mesh.\",\n \"properties\": {\n \"incoming\": {\n \"description\": \"Incoming defines the TLS configuration for inbound mTLS connections targeting the public listener on Connect and TerminatingGateway proxy kinds.\",\n \"properties\": {\n \"cipherSuites\": {\n \"description\": \"CipherSuites sets the default list of TLS cipher suites to support when negotiating connections using TLS 1.2 or earlier. If unspecified, Envoy will use a default server cipher list. The list of supported cipher suites can be seen in https://github.com/hashicorp/consul/blob/v1.11.2/types/tls.go#L154-L169 and is dependent on underlying support in Envoy. Future releases of Envoy may remove currently-supported but insecure cipher suites, and future releases of Consul may add new supported cipher suites if any are added to Envoy.\",\n \"items\": {\n \"type\": \"string\"\n },\n \"type\": \"array\"\n },\n \"tlsMaxVersion\": {\n \"description\": \"TLSMaxVersion sets the default maximum TLS version supported. Must be greater than or equal to `TLSMinVersion`. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy will default to TLS 1.3 as a max version for incoming connections.\",\n \"type\": \"string\"\n },\n \"tlsMinVersion\": {\n \"description\": \"TLSMinVersion sets the default minimum TLS version supported. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy v1.22.0 and newer will default to TLS 1.2 as a min version, while older releases of Envoy default to TLS 1.0.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"outgoing\": {\n \"description\": \"Outgoing defines the TLS configuration for outbound mTLS connections dialing upstreams from Connect and IngressGateway proxy kinds.\",\n \"properties\": {\n \"cipherSuites\": {\n \"description\": \"CipherSuites sets the default list of TLS cipher suites to support when negotiating connections using TLS 1.2 or earlier. If unspecified, Envoy will use a default server cipher list. The list of supported cipher suites can be seen in https://github.com/hashicorp/consul/blob/v1.11.2/types/tls.go#L154-L169 and is dependent on underlying support in Envoy. Future releases of Envoy may remove currently-supported but insecure cipher suites, and future releases of Consul may add new supported cipher suites if any are added to Envoy.\",\n \"items\": {\n \"type\": \"string\"\n },\n \"type\": \"array\"\n },\n \"tlsMaxVersion\": {\n \"description\": \"TLSMaxVersion sets the default maximum TLS version supported. Must be greater than or equal to `TLSMinVersion`. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy will default to TLS 1.3 as a max version for incoming connections.\",\n \"type\": \"string\"\n },\n \"tlsMinVersion\": {\n \"description\": \"TLSMinVersion sets the default minimum TLS version supported. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy v1.22.0 and newer will default to TLS 1.2 as a min version, while older releases of Envoy default to TLS 1.0.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n },\n \"transparentProxy\": {\n \"description\": \"TransparentProxy controls the configuration specific to proxies in \\\"transparent\\\" mode. Added in v1.10.0.\",\n \"properties\": {\n \"meshDestinationsOnly\": {\n \"description\": \"MeshDestinationsOnly determines whether sidecar proxies operating in \\\"transparent\\\" mode can proxy traffic to IP addresses not registered in Consul's catalog. If enabled, traffic will only be proxied to upstreams with service registrations in the catalog.\",\n \"type\": \"boolean\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"title\": \"Mesh\",\n \"type\": \"object\"\n}"} | ||
{"kind":"Mesh","apiVersion":"consul.hashicorp.com/v1alpha1","displayName":"Mesh","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","displayName":"CONSUL","category":"Orchestration \u0026 Management","subCategory":"Service Mesh"},"schema":"{\n \"description\": \"MeshSpec defines the desired state of Mesh.\",\n \"properties\": {\n \"http\": {\n \"description\": \"HTTP defines the HTTP configuration for the service mesh.\",\n \"properties\": {\n \"sanitizeXForwardedClientCert\": {\n \"type\": \"boolean\"\n }\n },\n \"required\": [\n \"sanitizeXForwardedClientCert\"\n ],\n \"type\": \"object\"\n },\n \"peering\": {\n \"description\": \"Peering defines the peering configuration for the service mesh.\",\n \"properties\": {\n \"peerThroughMeshGateways\": {\n \"description\": \"PeerThroughMeshGateways determines whether peering traffic between control planes should flow through mesh gateways. If enabled, Consul servers will advertise mesh gateway addresses as their own. Additionally, mesh gateways will configure themselves to expose the local servers using a peering-specific SNI.\",\n \"type\": \"boolean\"\n }\n },\n \"type\": \"object\"\n },\n \"tls\": {\n \"description\": \"TLS defines the TLS configuration for the service mesh.\",\n \"properties\": {\n \"incoming\": {\n \"description\": \"Incoming defines the TLS configuration for inbound mTLS connections targeting the public listener on Connect and TerminatingGateway proxy kinds.\",\n \"properties\": {\n \"cipherSuites\": {\n \"description\": \"CipherSuites sets the default list of TLS cipher suites to support when negotiating connections using TLS 1.2 or earlier. If unspecified, Envoy will use a default server cipher list. The list of supported cipher suites can be seen in https://github.com/hashicorp/consul/blob/v1.11.2/types/tls.go#L154-L169 and is dependent on underlying support in Envoy. Future releases of Envoy may remove currently-supported but insecure cipher suites, and future releases of Consul may add new supported cipher suites if any are added to Envoy.\",\n \"items\": {\n \"type\": \"string\"\n },\n \"type\": \"array\"\n },\n \"tlsMaxVersion\": {\n \"description\": \"TLSMaxVersion sets the default maximum TLS version supported. Must be greater than or equal to `TLSMinVersion`. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy will default to TLS 1.3 as a max version for incoming connections.\",\n \"type\": \"string\"\n },\n \"tlsMinVersion\": {\n \"description\": \"TLSMinVersion sets the default minimum TLS version supported. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy v1.22.0 and newer will default to TLS 1.2 as a min version, while older releases of Envoy default to TLS 1.0.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n },\n \"outgoing\": {\n \"description\": \"Outgoing defines the TLS configuration for outbound mTLS connections dialing upstreams from Connect and IngressGateway proxy kinds.\",\n \"properties\": {\n \"cipherSuites\": {\n \"description\": \"CipherSuites sets the default list of TLS cipher suites to support when negotiating connections using TLS 1.2 or earlier. If unspecified, Envoy will use a default server cipher list. The list of supported cipher suites can be seen in https://github.com/hashicorp/consul/blob/v1.11.2/types/tls.go#L154-L169 and is dependent on underlying support in Envoy. Future releases of Envoy may remove currently-supported but insecure cipher suites, and future releases of Consul may add new supported cipher suites if any are added to Envoy.\",\n \"items\": {\n \"type\": \"string\"\n },\n \"type\": \"array\"\n },\n \"tlsMaxVersion\": {\n \"description\": \"TLSMaxVersion sets the default maximum TLS version supported. Must be greater than or equal to `TLSMinVersion`. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy will default to TLS 1.3 as a max version for incoming connections.\",\n \"type\": \"string\"\n },\n \"tlsMinVersion\": {\n \"description\": \"TLSMinVersion sets the default minimum TLS version supported. One of `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, or `TLSv1_3`. If unspecified, Envoy v1.22.0 and newer will default to TLS 1.2 as a min version, while older releases of Envoy default to TLS 1.0.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n },\n \"transparentProxy\": {\n \"description\": \"TransparentProxy controls the configuration specific to proxies in \\\"transparent\\\" mode. Added in v1.10.0.\",\n \"properties\": {\n \"meshDestinationsOnly\": {\n \"description\": \"MeshDestinationsOnly determines whether sidecar proxies operating in \\\"transparent\\\" mode can proxy traffic to IP addresses not registered in Consul's catalog. If enabled, traffic will only be proxied to upstreams with service registrations in the catalog.\",\n \"type\": \"boolean\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"title\": \"Mesh\",\n \"type\": \"object\"\n}"} |
2 changes: 1 addition & 1 deletion
2
templates/meshmodel/components/v1.0.2/peeringacceptor.meshery.layer5.io_meshmodel.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
{"kind":"PeeringAcceptor","apiVersion":"consul.hashicorp.com/v1alpha1","display-name":"Peering Acceptor","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","display-name":"CONSUL","category":"Orchestration \u0026 Management","sub-category":"Service Mesh"},"schema":"{\n \"description\": \"PeeringAcceptorSpec defines the desired state of PeeringAcceptor.\",\n \"properties\": {\n \"peer\": {\n \"description\": \"Peer describes the information needed to create a peering.\",\n \"properties\": {\n \"secret\": {\n \"description\": \"Secret describes how to store the generated peering token.\",\n \"properties\": {\n \"backend\": {\n \"description\": \"Backend is where the generated secret is stored. Currently supports the value: \\\"kubernetes\\\".\",\n \"type\": \"string\"\n },\n \"key\": {\n \"description\": \"Key is the key of the secret generated.\",\n \"type\": \"string\"\n },\n \"name\": {\n \"description\": \"Name is the name of the secret generated.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"required\": [\n \"peer\"\n ],\n \"title\": \"Peering Acceptor\",\n \"type\": \"object\"\n}"} | ||
{"kind":"PeeringAcceptor","apiVersion":"consul.hashicorp.com/v1alpha1","displayName":"Peering Acceptor","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","displayName":"CONSUL","category":"Orchestration \u0026 Management","subCategory":"Service Mesh"},"schema":"{\n \"description\": \"PeeringAcceptorSpec defines the desired state of PeeringAcceptor.\",\n \"properties\": {\n \"peer\": {\n \"description\": \"Peer describes the information needed to create a peering.\",\n \"properties\": {\n \"secret\": {\n \"description\": \"Secret describes how to store the generated peering token.\",\n \"properties\": {\n \"backend\": {\n \"description\": \"Backend is where the generated secret is stored. Currently supports the value: \\\"kubernetes\\\".\",\n \"type\": \"string\"\n },\n \"key\": {\n \"description\": \"Key is the key of the secret generated.\",\n \"type\": \"string\"\n },\n \"name\": {\n \"description\": \"Name is the name of the secret generated.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"required\": [\n \"peer\"\n ],\n \"title\": \"Peering Acceptor\",\n \"type\": \"object\"\n}"} |
2 changes: 1 addition & 1 deletion
2
templates/meshmodel/components/v1.0.2/peeringdialer.meshery.layer5.io_meshmodel.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
{"kind":"PeeringDialer","apiVersion":"consul.hashicorp.com/v1alpha1","display-name":"Peering Dialer","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","display-name":"CONSUL","category":"Orchestration \u0026 Management","sub-category":"Service Mesh"},"schema":"{\n \"description\": \"PeeringDialerSpec defines the desired state of PeeringDialer.\",\n \"properties\": {\n \"peer\": {\n \"description\": \"Peer describes the information needed to create a peering.\",\n \"properties\": {\n \"secret\": {\n \"description\": \"Secret describes how to store the generated peering token.\",\n \"properties\": {\n \"backend\": {\n \"description\": \"Backend is where the generated secret is stored. Currently supports the value: \\\"kubernetes\\\".\",\n \"type\": \"string\"\n },\n \"key\": {\n \"description\": \"Key is the key of the secret generated.\",\n \"type\": \"string\"\n },\n \"name\": {\n \"description\": \"Name is the name of the secret generated.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"required\": [\n \"peer\"\n ],\n \"title\": \"Peering Dialer\",\n \"type\": \"object\"\n}"} | ||
{"kind":"PeeringDialer","apiVersion":"consul.hashicorp.com/v1alpha1","displayName":"Peering Dialer","format":"JSON","metadata":{},"model":{"name":"CONSUL","version":"v1.0.2","displayName":"CONSUL","category":"Orchestration \u0026 Management","subCategory":"Service Mesh"},"schema":"{\n \"description\": \"PeeringDialerSpec defines the desired state of PeeringDialer.\",\n \"properties\": {\n \"peer\": {\n \"description\": \"Peer describes the information needed to create a peering.\",\n \"properties\": {\n \"secret\": {\n \"description\": \"Secret describes how to store the generated peering token.\",\n \"properties\": {\n \"backend\": {\n \"description\": \"Backend is where the generated secret is stored. Currently supports the value: \\\"kubernetes\\\".\",\n \"type\": \"string\"\n },\n \"key\": {\n \"description\": \"Key is the key of the secret generated.\",\n \"type\": \"string\"\n },\n \"name\": {\n \"description\": \"Name is the name of the secret generated.\",\n \"type\": \"string\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"type\": \"object\"\n }\n },\n \"required\": [\n \"peer\"\n ],\n \"title\": \"Peering Dialer\",\n \"type\": \"object\"\n}"} |
Oops, something went wrong.