vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Transit Gateway 



 Resources Data sources 

 <br><br> * [ibm_tg_connection](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/tg_connection)<br> * [ibm_connection_prefix_filter](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/tg_connection_prefix_filter)<br> * [ibm_tg_gateway](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/tg_gateway)<br> * [ibm_tg_route_report](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/tg_route_report)<br><br><br> <br><br> * [ibm_tg_connection_prefix_filter](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/tg_connection_prefix_filter)<br> * [ibm_tg_connection_
[Network load balancer traffic flow](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/nlb-datapath.png)

Figure 2. Network load balancer traffic flow





 Related links 



* [Load balancer API reference](https://cloud.ibm.com/apidocs/vpclist-load-balancers)
* [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls)
* [Activity Tracker events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-load-balancers)
* [Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasload-balancer-quotas)
404 The specified Transit Gateway could not be found, the specified resource group could not be found, or the default resource group could not be found (if the resource group was not specified in the template). 
 409 The network being connected must either be in a location that is considered "local" to the specified Transit Gateway, or the specified Transit Gateway needs to be global. The network being connected cannot already be connected to another Transit Gateway. 





 Example Response 

This example response illustrates that the connection was created successfully:

{
"name": "Transit_Service_BWTN_SJ_DL",
"network_id": "crn:v1:bluemix:public:is:us-south:a/123456::vpc:4727d842-f94f-4a2d-824a-9bc9b02c523b",
"network_type": "vpc",
"id": "1a15dca5-7e33-45e1-b7c5-bc690e569531",
"base_connection_id": "975f58c1-afe7-469a-9727-7f3d720f2d32",
"created_at": "2022-02-18T16:51:50.748Z",
"local_bgp_asn": 64490,
"local_gateway_ip": "192.168.100.1",
"local_tunnel_ip": "192.168.129.2",
"mtu": 9000,
"network_account_id": "28e4d90ac7504be694471ee66e70d0d5",
"prefix_filters": [
{
"action": "permit",
"before": "1a15dcab-7e40-45e1-b7c5-bc690eaa9782",
"created_at": "2022-02-18T16:51:50.748Z",
Use the following table to document the parameters you need for your deployment. Examples are shown that match the deployment described previously.



Table 12. PowerNSX DLR parameters

 Parameters Example Your deployment 

 vCenter Server IP address 
 vCenter Server user 
 vCenter Server password 
 AD DNS server IP address 10.187.214.66 
 Transit Logical Switch OpenShift-Transit 
 OpenShift network 192.168.133.0/24 
 Transit network 192.168.100.0/24 
 ESG transit 192.168.100.1 
 DLR transit 192.168.100.2 
 ESG name OpenShift-ESG 
 vCenter Server instance cluster cluster1 
 vCenter Server instance datastore vsanDatastore 
 Private portable subnet 10.208.242.128/26 
 BCR IP address 10.208.242.129 
 ESG private primary 10.208.242.130 
 ESG private secondary 1 10.208.242.131 
 ESG private secondary 2 10.208.242.132 
 ESG private secondary 3 10.208.242.133 
 Public portable subnet 169.48.73.40/29 
 FCR IP address 169.48.73.41 
 ESG public primary 169.48.73.42 
 ESG public secondary 1 169.48.73.43 
 ESG public secondary 2 169.48.73.44 
 ESG username admin 
 ESG password VMware12345! 



 Connect to NSX Manager
Connect-NsxServer -vCenterServer <IP_Address> -User <UserName> -Password '<Password>'

 Create Edge interface specification and create Edge
$priUplink = New-NsxEdgeInterfaceSpec -index 0 -Name "Private Uplink" -Type Uplink -ConnectedTo (Get-VDPortgroup SDDC-DPortGroup-Mgmt) -PrimaryAddress 10.208.242.130 -SubnetPrefixLength 26 -SecondaryAddresses 10.208.242.131,10.208.242.132,10.208.242.133
* [Removing the Azure File storage configuration from the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazure-file-template-rm-cli)



* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazurefile-csi-driver-parameter-reference)



* [1.9.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazurefile-csi-driver-1.9.0-parameters)
* [1.18.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazurefile-csi-driver-1.18.0-parameters)
* [1.22.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazurefile-csi-driver-1.22.0-parameters)



* [Storage class reference for Azure File](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driverazure-file-sc-ref)
* [Getting help and support for Azure File storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-azurefile-csi-driversat-azure-file-support)







 Google storage templates 

[Google Compute Engine persistent disk Container Storage Interface (CSI) Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driverstorage-gcp-compute-persistent-disk-csi-driver)



* [Prerequisites](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driversat-storage-gcp-csi-prereq)
"errors": [
{
"code": "missing_field",
"message": "The location field is required.",
"more_info": "https://transitservice.cloud.ibm.com/",
"target": {
"name": "location",
"type": "field"
}
}
],
"trace": "86780a34-e651-4b47-9fb0-184a169cc9af"
}

For more information (including Java, Node, Python and Go examples), see "Add Connection to a Transit Gateway" and "Perform actions on a connection for a Transit Gateway" in the [Transit Gateway API reference](https://cloud.ibm.com/apidocs/transit-gateway?code=javacreate-transit-gateway-connection).
* [Exploring IBM Cloud load balancers](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-explore)
* [Citrix VPX Product Lifecycle](https://www.citrix.com/support/product-lifecycle/product-matrix.html)
* [What is load balancing?](https://www.ibm.com/cloud/learn/load-balancing)
* [Release notes for Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-citrix-netscaler-vpx-release-notes)



* How to



* [Managing your Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-managing-your-citrix-netscaler-vpx)
* [Upgrading your Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-upgrading-your-citrix-netscaler-vpx)
* [Setting up Citrix Netscaler VPX for High Availability (HA)](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-setting-up-citrix-netscaler-vpx-for-high-availability-ha-)
* [Setting up Citrix Netscaler VPX as a forwarding proxy](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-setting-up-citrix-netscaler-vpx-as-a-forwarding-proxy)
* Configuring forward-proxy traffic redirection using the Citrix Netscaler VPX appliance
SportsLeagueChampionshipEvent 
 SportsLeagueDraft 
 SportsOfficial 
 SportsTeam 
 Stadium 
 Star 
 StarSystem 
 StarSystemBody 
 Station 
 Supercouple 
 Symptom 
 Synthesizer 
 Telescope 
 TelescopePlatform 
 TelevisionShow 
 TennisPlayer 
 TennisTournament 
 Theater 
 TheaterCharacter 
 TheaterProduction 
 TopLevelDomainRegistry 
 TouristAttraction 
 Tower 
 TradeUnion 
 TransitLine 
 TransportOperator 
 TransportTerminus 
 TropicalCyclone 
 TVActor 
 TVCharacter 
 TVCrewRole 
 TVEpisode 
 TVNetwork 
 TVPersonality 
 TVProducer 
 TVSeason 
 TVWriter 
 TypeOfPlaceOfWorship 
 UnfinishedWork 
 UnitOfMass 
 UnitOfVolume 
 University 
 U.S.Congressperson 
 Vein 
 VideoGame 
 VideoGameDesigner 
 VideoGameDeveloper 
 VideoGameEngine 
 VideoGamePlatform 
 VideoGamePublisher 
 VisualArtist 
 WebBrowserExtension 
 Website 
 WineProducer 
 WineRegion 
 WorkOfFiction 
 Writer
* ibmcloud is load-balancer-listener-policy-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --name my-policy --priority 5
* ibmcloud is load-balancer-listener-policy-update my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 my-lblp --name my-policy --priority 5
* ibmcloud is load-balancer-listener-policy-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --action forward --target 70294e14-4e61-11e8-bcf4-0242ac110004 When the action is forward, the pool ID or name is required to specify which pool the load balancer forwards the traffic to.
* ibmcloud is load-balancer-listener-policy-update my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 my-policy --action forward --target my-pool When the action is forward, the pool ID or name is required to specify which pool the load balancer forwards the traffic to.
2022/05/31 12:19:31 Terraform apply | "max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct""
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Expires": [
2022/05/31 12:19:31 Terraform apply | "-1"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Pragma": [
2022/05/31 12:19:31 Terraform apply | "no-cache"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Server": [
2022/05/31 12:19:31 Terraform apply | "cloudflare"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Strict-Transport-Security": [
2022/05/31 12:19:31 Terraform apply | "max-age=31536000; includeSubDomains"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Vary": [
2022/05/31 12:19:31 Terraform apply | "Accept-Encoding"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "X-Content-Type-Options": [
2022/05/31 12:19:31 Terraform apply | "nosniff"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "X-Request-Id": [
network-acl is.network-acl.rule.read One or more network ACL rules was retrieved 







 Custom route events 

The following table lists the actions that are related to VPC routing tables and routes.



Table 2. Actions that generate events for VPC routing tables and routes

 Resource Action Description 

 routing table is.vpc.routing-table.create Routing table was created 
 routing table is.vpc.routing-table.update Routing table was updated 
 routing table is.vpc.routing-table.delete Routing table was deleted 
 routing table is.vpc.routing-table.read Routing table was retrieved (get and list) 
 route is.vpc.routing-table_route.create Routing table route was created 
 route is.vpc.routing-table_route.update Routing table route was updated 
 route is.vpc.routing-table_route.delete Routing table route was deleted 
 route is.vpc.routing-table_route.read Routing table route was retrieved (get and list) 
 subnet is.subnet.routing-table.read Subnets attached to a routing table were retrieved 
 subnet is.subnet.routing-table.attach Routing table was attached to a subnet 







 Flow log events 

The following table lists the actions that are related to flow logs and the generation of events.



Table 4. Actions that generate events for flow log collectors

 Resource Action Description 

 flow-log-collector is.flow-log-collector.flow-log-collector.create Flow log collector was created 
 flow-log-collector is.flow-log-collector.flow-log-collector.delete Flow log collector was deleted 
 flow-log-collector is.flow-log-collector.flow-log-collector.read Flow log collector was read 
 flow-log-collector is.flow-log-collector.flow-log-collector.update Flow log collector was updated 







 Load balancer events 

The following table lists the actions that are related to load balancers and the generation of events.



Table 5. Actions that generate events for load balancers

 Resource Action Description 

 Load balancer is.load-balancer.load-balancer.create Load balancer was created
Check out [Migrating your service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-bind).
5. Scaling, high availability, and traffic management (current page)
6. Find [Code Engine equivalents to Cloud Foundry commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-cmd).
7. Still have questions? Try the [Migrating Cloud Foundry applications to Code Engine FAQ](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faq).



Other information



* Find out about [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).
* Try other [Code Engine tutorials](https://cloud.ibm.com/docs?tab=tutorials&tags=codeengine&page=1&pageSize=20).
* Explore other [Code Engine topics](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-paths).
About IBM Cloud Network Load Balancer for VPC 

You can use the IBM Cloud® Network Load Balancer for VPC (NLB) to distribute traffic among multiple server instances within the same region of your VPC.

The following diagram illustrates the deployment architecture for a network load balancer.

Zoom

![Network load balancer for VPC](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/nlb_arc.png)

Network load balancer

Network load balancers can accept members across all three availability zones, but the NLB itself resides in one specific zone. For more information, see [Multi-zone support](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elbnlb-mz-support).



 Getting started 

To configure a network load balancer, make sure that you have met the following prerequisites:



* If you don't have a VPC, create a VPC in the region that you want to create your NLB.
* Create a subnet in your preferred zone in your VPC.
* Create instances. You can also attach instances to your load balancer later.



After you completed all prerequisites, you can create your NLB. For more information, see [Creating a network load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer).





 Types of network load balancers 

Network Load Balancer for VPC supports public, private, and private-type with routing mode enabled.

A public load balancer is a load balancer with a publicly accessible IP address that is registered with DNS. A private load balancer is a load balancer only accessible from within the VPC network and/or where the client has reachability to the VPC network (for example, through Direct Link or Transit Gateway).
13.100.0.0/24 from VPC A subnet 
 10.101.0.0/24 from VPC B through Transit Gateway (local) 
 13.101.0.0/24 from VPC B through Transit Gateway (local) 
 10.111.0.0/24 from VPC Z through Transit Gateway (global) 
 13.111.0.0/24 from VPC Z through Transit Gateway (global) 



VPC A Default (Egress) Routing Table

VPC B Default (Egress) Routing Table

VPC Z Default (Egress) Routing Table



Table 11. VPC A Default (Egress) Routing Table

 Destination Action Next Hop Location 

 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 1 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 2 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 3 







 Use case 3: VPC-to-classic and BCR peering with IBM Cloud Transit Gateway 

Zoom

![VPC-to-classic and BCR peering with Transit Gateway use case](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/vpc-classic-transit-gateway.png)

VPC-to-classic and BCR peering with Transit Gateway use case

VPC A Networks



Table 14. VPC B Networks

 IP Origin 

 10.100.0.0/24 from VPC A subnet 
 13.100.0.0/24 from VPC A subnet 
 13.111.0.0/24 from Classic through Transit Gateway 



VPC A Default (Egress) Routing Table



Table 15. VPC A Default (Egress) Routing Table

 Destination Action Next Hop Location
Range 1-65535.
* --port-min: The inclusive lower bound of the range of ports that are used by this listener. Must not be greater than port_max. Currently, only load balancers that are operating with route mode enabled and public load balancers in the network family support more than one port per listener. Listeners in the load balancer with the same protocol must have nonoverlapping port ranges. Range 1-65535.
* --port-max: The inclusive higher bound of the range of ports that are used by this listener. Must not be less than port_min. Currently, only load balancers that are operating with route mode enabled and public load balancers in the network family support more than one port per listener. Listeners in the load balancer with the same protocol must have nonoverlapping port ranges. Range 1-65535.
* --default-pool: ID of the default pool.
* --connection-limit: The maximum number of connections of the listener. This option is not applicable for the load balancers in the network family.
* --certificate-instance-crn: The certificate instance CRN used for SSL termination. Required when protocol is https. This option is not applicable for the load balancers in the network family.
* --policies: LISTENER_POLICIES_JSON | @LISTENER_POLICIES_JSON_FILE, listener policies in JSON or JSON file. This option is not applicable for the load balancers in the network family.
* --accept-proxy-protocol: If set to true, proxy protocol is enabled for this listener. Only supported for application load balancers. One of: false, true.
* --http-redirect-listener-id: ID of the listener that is set as the HTTP redirect target.
* --http-redirect-status-code: The HTTP status code that is returned in the redirect response. One of: 301, 302, 303, 307, 308.
* --http-redirect-target-uri: Target URI where traffic is redirected.
"departure":"Flight DL1040 departs on 2019-02-02 at 16:45."
},
{
"arrival":"Flight DL1710 arrives on 2019-02-02 at 10:19.",
"departure":"Flight DL1710 departs on 2019-02-02 at 07:00."
},
{
"arrival":"Flight DL4379 arrives on 2019-02-03 at 09:05.",
"departure":"Flight DL4379 departs on 2019-02-02 at 21:40."
}
]

Notice that the order of the arrival and departure elements is swapped in the response. The service typically reorders elements in a JSON Object. If you want the elements to be returned in a specific order, define the template by using a JSON Array or String value instead.







 JSONArray.remove(Integer) 

This method removes the element in the index position from the JSONArray and returns the updated JSONArray.

For this Dialog runtime context:

{
"context": {
"toppings_array": ["onion", "olives"]
}
}

Make this update:

{
"context": {
"toppings_array": "<? $toppings_array.remove(0) ?>"
}
}

Result:

{
"context": {
"toppings_array": ["olives"]
}
}





 JSONArray.removeValue(object) 

This method removes the first occurrence of the value from the JSONArray and returns the updated JSONArray.

For this Dialog runtime context:

{
"context": {
"toppings_array": ["onion", "olives"]
}
}

Make this update:

{
"context": {
"toppings_array": "<? $toppings_array.removeValue('onion') ?>"
: Annotation to specify a private or public load balancer.

service.kubernetes.io/ibm-load-balancer-cloud-provider-zone:
: Annotation to specify the zone that the load balancer service deploys to. To see zones, run ibmcloud oc zone ls.

service.kubernetes.io/ibm-load-balancer-cloud-provider-vlan:
: Annotation to specify a VLAN that the load balancer service deploys to. To see VLANs, run ibmcloud oc vlan ls --zone <zone>.

service.kubernetes.io/ibm-load-balancer-cloud-provider-enable-features: "ipvs"
: Annotation to specify a version 2.0 load balancer.

service.kubernetes.io/ibm-load-balancer-cloud-provider-ipvs-scheduler:
: Optional: Annotation to specify the scheduling algorithm. Accepted values are "rr" for round-robin (default) or "sh" for Source Hashing. For more information, see [2.0: Scheduling algorithms](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-v2scheduling).

selector
: The label key (<selector_key>) and value (<selector_value>) that you used in the spec.template.metadata.labels section of your app deployment YAML.

port
: The port that the service listens on.

loadBalancerIP
: Optional: To create a private NLB or to use a specific portable IP address for a public NLB, specify the IP address that you want to use. The IP address must be in the zone and VLAN that you specify in the annotations. If you don't specify an IP address: If your cluster is on a public VLAN, a portable public IP address is used. Most clusters are on a public VLAN. If your cluster is on a private VLAN only, a portable private IP address is used.

externalTrafficPolicy: Local
: Set to Local.
* [4.10 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-remoteodf-remote-4.10-parameters)
* [4.11 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-remoteodf-remote-4.11-parameters)
* [4.12 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-remoteodf-remote-4.12-parameters)



* [Storage class reference for OpenShift Data Foundation for remote devices](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-remotesat-storage-odf-remote-sc-ref)







 VMware storage templates 

[VMware Block Container Storage Interface (CSI) Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driverstorage-vsphere-csi-driver)



* [Prerequisites](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driverprereq-vmware-csi)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervsphere-csi-driver-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervsphere-csi-driver-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervsphere-csi-driver-config-create-api)
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --accept-proxy-protocol true
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --port-min 80 --port-max 85 The range of ports that are used by this listener.
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --http-redirect-listener-id d7e0543c-4e0f-4c0d-89aa-73f0f028ec61 --http-redirect-status-code 303
* ibmcloud is load-balancer-listener-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --http-redirect-listener-id d7e0543c-4e0f-4c0d-89aa-73f0f028ec61 --http-redirect-status-code 307 --http-redirect-target-uri /example2