remove reference to HTTPPipeline in doc (#719)

easegress-io · Jul 25, 2022 · c992926 · c992926
1 parent 085130a
commit c992926
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 102 deletions.
diff --git a/doc/reference/controllers.md b/doc/reference/controllers.md
@@ -66,7 +66,7 @@ The drivers need to offer notifying change periodically, and operations to the e
 
 ### TrafficController
 
-TrafficController handles the lifecycle of HTTPServer and HTTPPipeline and their relationship. It manages the resource in a namespaced way. HTTPServer accepts incoming traffic and routes it to HTTPPipelines in the same namespace. Most other controllers could handle traffic by leverage the ability of TrafficController..
+TrafficController handles the lifecycle of Traffic Gates (like HTTPServer) and Pipeline and their relationship. It manages the resource in a namespaced way. Traffic gates accepts incoming traffic and routes it to Pipelines in the same namespace. Most other controllers could handle traffic by leverage the ability of TrafficController..
 
 ### RawConfigTrafficController
 

diff --git a/doc/reference/wasmhost.md b/doc/reference/wasmhost.md
@@ -285,7 +285,7 @@ The `wasm-pipeline` configuration is (we will adjust the value of `maxConcurrenc
 ```bash
 $ echo '
 name: wasm-pipeline
-kind: HTTPPipeline
+kind: Pipeline
 flow:
 - filter: wasm
 filters:
@@ -301,7 +301,7 @@ The `mock-pipeline` configuration is:
 ```bash
 $ echo '
 name: mock-pipeline
-kind: HTTPPipeline
+kind: Pipeline
 flow:
 - filter: mock
 filters:

diff --git a/example/config/http-pipeline-orchestration.yaml b/example/config/http-pipeline-orchestration.yaml
diff --git a/example/config/http-pipeline-example.yaml → example/config/pipeline-example.yaml b/example/config/http-pipeline-example.yaml → example/config/pipeline-example.yaml
@@ -1,15 +1,14 @@
 name: http-pipeline-example
-kind: HTTPPipeline
+kind: Pipeline
 
 # Built-in labels are `END` which can't be used by filters.
 flow:
  - filter: validator
  jumpIf: { invalid: END }
- # - filter: fallback
  - filter: rateLimiter
  - filter: requestAdaptor
  - filter: proxy
- jumpIf: { fallback: END }
+ jumpIf: { clientError: END }
  - filter: responseAdaptor
 
 filters:
@@ -70,13 +69,6 @@ filters:
  add: {}
  - name: proxy
  kind: Proxy
- failureCodes: [500, 501]
- fallback:
- forCodes: true
- forCircuitBreaker: false
- mockCode: 200
- mockHeader: {X-Fallback: yes}
- mockBody: '{"message": "Backend failed, try it later."}'
  mirrorPool:
  servers:
  - url: http:https://127.0.0.1:9091
@@ -88,20 +80,19 @@ filters:
  headers:
  X-Filter:
  exact: mirror
- candidatePools:
- - servers:
- - url: http:https://127.0.0.1:9093
- - url: http:https://127.0.0.1:9094
- loadBalance:
- policy: random
- headerHashKey: ""
- memoryCache: null
- filter:
- headers:
- X-Filter:
- exact: candidate
- mainPool:
- serviceRegistry: nacos-service-registry-example
+ pools:
+ - servers:
+ - url: http:https://127.0.0.1:9093
+ - url: http:https://127.0.0.1:9094
+ loadBalance:
+ policy: random
+ headerHashKey: ""
+ memoryCache: null
+ filter:
+ headers:
+ X-Filter:
+ exact: candidate
+ - serviceRegistry: nacos-service-registry-example
  serviceName: service-001
  serversTags: ["v2"]
  servers:
@@ -116,16 +107,6 @@ filters:
  loadBalance:
  policy: roundRobin
  headerHashKey: X-User-Id
- # memoryCache:
- # expiration: 10s
- # maxEntryBytes: 4096
- # size: 100
- # codes:
- # - 200
- # - 201
- # methods:
- # - GET
- # - HEAD
  compression:
  minLength: 1024
  - name: responseAdaptor

diff --git a/example/config/remote-pipeline.yaml b/example/config/remote-pipeline.yaml
@@ -1,5 +1,5 @@
 name: remote-pipeline
-kind: HTTPPipeline
+kind: Pipeline
 
 filters:
  - name: remoteFilter