vania-janet/multiturn-rag-retrieval-data huggingface dataset:
-n, --name NAME
: Policy name.

-a, --action TYPE
: Policy action: REJECT | REDIRECT_POOL | REDIRECT_URL.

-r, --redirect INPUT
: URL or POOL_UUID. It's only available in REDIRECT_POOL | REDIRECT_URL action.

-p --priority PRIORITY
: Policy priority.





 Examples 

ibmcloud sl loadbal l7policy-add --protocol-uuid 27204f2c-1853-4fd2-9c97-1654cd536edd -n my-policy -a REJECT







 ibmcloud sl loadbal l7policy-delete 

Delete an L7 pool:

ibmcloud sl loadbal l7policy-delete (--policy-id POLICY_ID) [-f, --force]



 Command options 

--policy-id ID (required)
: ID for the load balancer policy.

-f, --force
: Force operation without confirmation.





 Examples 

ibmcloud sl loadbal l7policy-delete --policy-id 27204f2c-1853-4fd2-9c97-1654cd536edd -f







 ibmcloud sl loadbal l7pool-add 

Add an L7 pool:

ibmcloud sl loadbal l7pool-add (--id LOADBAL_ID) (-n, --name NAME) [-m, --method METHOD] [-s, --server BACKEND_IP:PORT] [-p, --protocol PROTOCOL] [--health-path PATH] [--health-interval INTERVAL] [--health-retry RETRY] [--health-timeout TIMEOUT] [--sticky cookie | source-ip]



 Command options 

--id ID (required)
: ID for the load balancer.

-n, --name NAME (required)
: Name for this L7 pool.

-m, --method
You can specify the following argument references for your resource when changing the configuration of your transit gateway using Terraform:



Table 1. Terraform argument references for changing the configuration

 Argument Details 

 name <br>Required <br>Boolean The unique user-defined name for the gateway. For example, myGateway 
 global <br>Required <br>Boolean The gateways with global routing (true) to connect to the networks outside their associated region. 





 Example 

This example illustrates changing the configuration of your transit gateway:

resource "ibm_tg_gateway" "new_tg_gw"{
name="transit-gateway-1"
location="us-south"
global=true
resource_group="30951d2dff914dafb26455a88c0c0092"
}
[BI.S4.H2.192 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13475&packageId=1109&presetId=1087) 32 64 192 GB 82,470 OLAP/OLTP (**) <br>SAP Business One (***) 
 [BI.S4.H2.384 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13475&packageId=1109&presetId=1091) 32 64 384 GB 85,130 OLAP/OLTP (**) <br>SAP Business One (***) 
 [BI.S4.H2.768 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13475&packageId=1109&presetId=1095) 40 80 768 GB 112,830 OLAP/OLTP (**) <br>SAP Business One (***) 
 [BI.S4.H2.1500 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1109&presetId=1099) 56 112 1536 GB 147,220 OLAP/OLTP (**) 
 [BI.S4.H2.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1109&presetId=1103) 56 112 3072 GB 135,127 OLAP/OLTP (**) 
 [BI.S4.H4.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1117&presetId=1117) 112 224 3072 GB 285,970 OLAP/OLTP (**)
ocs-operator-9d6457dff-c4xhh 1/1 Running 0 9m42s
rook-ceph-crashcollector-169.48.170.83-89f6d7dfb-gsglz 1/1 Running 0 5m38s
rook-ceph-crashcollector-169.48.170.88-6f58d6489-b9j49 1/1 Running 0 5m29s
rook-ceph-crashcollector-169.48.170.90-866b9d444d-zk6ft 1/1 Running 0 5m15s
rook-ceph-drain-canary-169.48.170.83-6b885b94db-wvptz 1/1 Running 0 4m41s
rook-ceph-drain-canary-169.48.170.88-769f8b6b7-mtm47 1/1 Running 0 4m39s
rook-ceph-drain-canary-169.48.170.90-84845c98d4-pxpqs 1/1 Running 0 4m40s
rook-ceph-mds-ocs-storagecluster-cephfilesystem-a-6dfbb4fcnqv9g 1/1 Running 0 4m16s
rook-ceph-mds-ocs-storagecluster-cephfilesystem-b-cbc56b8btjhrt 1/1 Running 0 4m15s
rook-ceph-mgr-a-55cc8d96cc-vm5dr 1/1 Running 0 4m55s
rook-ceph-mon-a-5dcc4d9446-4ff5x 1/1 Running 0 5m38s
rook-ceph-mon-b-64dc44f954-w24gs 1/1 Running 0 5m30s
rook-ceph-mon-c-86d4fb86-s8gdz 1/1 Running 0 5m15s
SecretSidecarMemoryRequest: "20Mi" container:storage-secret-sidecar, resource-type: memory-request
CSIProvisionerCPURequest: "20m" container:csi-provisioner, resource-type: cpu-request
CSIProvisionerMemoryRequest: "40Mi" container:csi-provisioner, resource-type: memory-request
CSIAttacherCPURequest: "15m" container:csi-attacher, resource-type: cpu-request
CSIAttacherMemoryRequest: "30Mi" container:csi-attacher, resource-type: memory-request
CSIResizerCPURequest: "20m" container:csi-resizer, resource-type: cpu-request
CSIResizerMemoryRequest: "40Mi" container:csi-resizer, resource-type: memory-request
BlockDriverCPURequest: "75m" container:iks-vpc-block-driver, resource-type: cpu-request
BlockDriverMemoryRequest: "150Mi" container:iks-vpc-block-driver, resource-type: memory-request
CSISnapshotterCPURequest: "20m" container:csi-snapshotter, resource-type: cpu-request
CSISnapshotterMemoryRequest: "40Mi" container:csi-snapshotter, resource-type: memory-request
Resource Limits per container
CSIDriverRegistrarCPULimit: "40m" container:csi-driver-registrar, resource-type: cpu-limit
CSIDriverRegistrarMemoryLimit: "80Mi" container:csi-driver-registrar, resource-type: memory-limit
NodeDriverCPULimit: "120m" container:iks-vpc-block-node-driver, resource-type: cpu-limit
NodeDriverMemoryLimit: "300Mi" container:iks-vpc-block-node-driver, resource-type: memory-limit
LivenessProbeCPULimit: "20m" container:liveness-probe, resource-type: cpu-limit
VPC-to-VPC connected with Transit Gateway

VPC A Networks

VPC B Networks

VPC Z Networks



Table 8. VPC A Networks

 IP Origin 

 10.100.0.0/24 from VPC A subnet 
 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/b698ea8660e1f51664f7479f870bbf8840335d06/dl/includes/vpc/includes/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
VPC-to-VPC connected with Transit Gateway

VPC A Networks

VPC B Networks

VPC Z Networks



Table 8. VPC A Networks

 IP Origin 

 10.100.0.0/24 from VPC A subnet 
 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/6a28e4ae2660b609a18e90e1239ed772f80373d6/transit-gateway/includes/vpc/includes/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
2020/01/10 21:27:50 Terraform plan | whitelist.1413716549.address: "172.16.2.0/24"
2020/01/10 21:27:50 Terraform plan | whitelist.1413716549.description: "subnet2"
2020/01/10 21:27:50 Terraform plan | whitelist.3438994501.address: "172.16.1.0/24"
2020/01/10 21:27:50 Terraform plan | whitelist.3438994501.description: "subnet1"
2020/01/10 21:27:50 Terraform plan 
2020/01/10 21:27:50 Terraform plan | -/+ ibm_is_lb_pool_member.lb1-pool-member1 (new resource required)
2020/01/10 21:27:50 Terraform plan | id: "r006-11cb7734-e05c-405b-9e35-20e05bc2766f/r006-d917d290-071a-4da1-a995-91262ea89f2c/r006-4b9b871a-b835-4cdc-9a87-e9423a6d7a12" => <computed> (forces new resource)
2020/01/10 21:27:50 Terraform plan | health: "ok" => <computed>
2020/01/10 21:27:50 Terraform plan | href: "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/r006-11cb7734-e05c-405b-9e35-20e05bc2766f/pools/r006-d917d290-071a-4da1-a995-91262ea89f2c/members/r006-4b9b871a-b835-4cdc-9a87-e9423a6d7a12" => <computed>
"network_type": "vpc",
"prefix_filters": [
{
"action": "permit",
"ge": 0,
"le": 32,
"prefix": "192.168.100.0/24"
}
],
"prefix_filters_default": "permit",
"remote_bgp_asn": 65010,
"remote_gateway_ip": "10.242.63.12",
"remote_tunnel_ip": "192.168.129.1"







 Response 

The following response shows once you initiate the request:



Table 3. Initiation request

 Response Body Details 

 name <br>Always included* <br>Name The user-defined name for this transit gateway connection. <br>Possible values: 1 ≤ length ≤ 63, Value must match regular expression `^([a-zA-Z] 
 network_type <br>Always included* <br>string Defines what type of network is connected via this connection. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [classic,directlink,gre_tunnel,unbound_gre_tunnel,vpc] <br>Example:vpc 
 id <br>Always included* <br>string The unique identifier for this Transit Gateway Connection <br>Example:1a15dca5-7e33-45e1-b7c5-bc690e569531 
 created_at <br>Always included* <br>date-time The date and time that this connection was created 
 network_id <br>string The ID of the network being connected via this connection. This field is required for some types, such as vpc and directlink For network types vpc and directlink it should be the CRN of the target vpc / gateway respectively.
2020/01/10 21:27:50 Terraform plan | href: "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/r006-11cb7734-e05c-405b-9e35-20e05bc2766f/pools/r006-d917d290-071a-4da1-a995-91262ea89f2c/members/r006-5418feb7-2169-47c3-8c71-66a86fec6d9a" => <computed>
2020/01/10 21:27:50 Terraform plan | lb: "r006-11cb7734-e05c-405b-9e35-20e05bc2766f" => "r006-11cb7734-e05c-405b-9e35-20e05bc2766f"
2020/01/10 21:27:50 Terraform plan | pool: "r006-d917d290-071a-4da1-a995-91262ea89f2c" => "r006-11cb7734-e05c-405b-9e35-20e05bc2766f/r006-d917d290-071a-4da1-a995-91262ea89f2c" (forces new resource)
2020/01/10 21:27:50 Terraform plan | port: "80" => "80"
2020/01/10 21:27:50 Terraform plan | provisioning_status: "active" => <computed>
2020/01/10 21:27:50 Terraform plan | target_address: "172.16.2.4" => "172.16.2.4"
2020/01/10 21:27:50 Terraform plan | weight: "50" => <computed>
2020/01/10 21:27:50 Terraform plan | Plan: 3 to add, 0 to change, 2 to destroy.
1_tl_Configure_20cache_20redirection_20for_20HTTP_28S_29_20traffic_20_7C_20IBM_20Cloud_20Docs_p_https_3A_2F_2Fcloud.ibm.com_2Fdocs_2Fcitrix-netscaler-vpx_3Ftopic_3Dcitrix-netscaler-vpx-configure-cache-redirection-for-http-traffic_r_lt_705_evt_pageLoad_sv_1_rn_320233](https://bat.bing.com/action/0?ti=146001191&Ver=2&mid=0221f76f-495c-4b72-8f9a-5b8c8b0894f4&sid=cca51480229211eeac887b94c5a6c542&vid=cca50460229211ee874f7dc32b9b9a8d&vids=0&msclkid=N&pi=918639831&lg=en-US&sw=3840&sh=2160&sc=30&nwd=1&tl=Configure%20cache%20redirection%20for%20HTTP%28S%29%20traffic%20%7C%20IBM%20Cloud%20Docs&p=https%3A%2F%2Fcloud.ibm.com%2Fdocs%2Fcitrix-netscaler-vpx%3Ftopic%3Dcitrix-netscaler-vpx-configure-cache-redirection-for-http-traffic&r=&lt=705&evt=pageLoad&sv=1&rn=320233)
* 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.
* ibmcloud is load-balancer-listener-policy-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --target-http-status-code 301 --target-url "https://www.redirect.com" When the action is redirect, the "url" and "http_status_code" are required. Possible values for http_status_code are "301", "302", "303", "307", or "308". The "url" is the redirect target URL.
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-9ca2000007-f0000d-400000e-8b02-ed6b000000",
"creation_date": "2022-01-25T19:22:04Z",
"crn": "crn:v1:bluemix:public:secrets-manager:eu-gb:a/00000a6bbea644a6be000000001f5:5f1a000000-5f000-4000-8bfc-5eef00000:secret:00000ea8e-7d00-00ce-c00a-0a0000f000ee",
"description": "Extended description for my secret.",
"downloaded": false,
"id": "00000ea00-7d0000-0000ce-c0002a-0a0000f4b3ee",
"labels": [],
"last_update_date": "2022-01-27T21:05:25Z",
"name": "test-kv-secret",
"secret_data": {
"payload": {
"key7": "value7"
}
},
"secret_type": "kv",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-9ca2000007-f0000d-400000e-8b02-ed6b000000",
"creation_date": "2022-01-25T19:22:04Z",
"downloaded": true,
"id": "00000ea00-7d0000-0000ce-c0002a-0a0000f4b3ee",
Osaka private.jp2.icr.io 166.9.70.4, 166.9.71.5, 166.9.72.6 166.9.247.39, 166.9.247.73, 166.9.247.105 
 Sao Paolo private.br.icr.io 166.9.82.13, 166.9.83.13, 166.9.84.13 166.9.246.72, 166.9.246.104, 166.9.246.130 
 Toronto private.ca.icr.io 166.9.76.12, 166.9.77.11, 166.9.78.11 166.9.247.143, 166.9.247.170, 166.9.247.207 
 UK South private.uk.icr.io 166.9.36.19, 166.9.38.14, 166.9.34.12 166.9.244.9, 166.9.244.45, 166.9.244.73 
 US East, US South private.us.icr.io 166.9.12.227, 166.9.15.116, 166.9.16.244 166.9.250.214, 166.9.250.246, 166.9.251.21 







 Optional: Set up allowlist rules for IBM Log Analysis and IBM Cloud Monitoring services 

To send logging and metric data, set up allowlist rules for your IBM Log Analysis and IBM Cloud Monitoring services.



* [Log Analysis private endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api_private)
* [Monitoring private endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_monitoring)









 Opening ports in a public or private allowlist for inbound traffic 

You can allow incoming access to NodePort, load balancer, and Ingress services, and Red Hat OpenShift routes.

NodePort service
: Open the port that you configured when you deployed the service to the public or private IP addresses for all the worker nodes to allow traffic to. To find the port, run oc get svc.
US East (mon01, tor01, wdc04, wdc06, wdc07) 166.9.20.11, 166.9.20.117, 166.9.20.12, 166.9.20.13, 166.9.20.187, 166.9.20.38, 166.9.20.42, 166.9.20.63, 166.9.20.80, 166.9.22.10, 166.9.22.109, 166.9.22.211, 166.9.22.215, 166.9.22.26, 166.9.22.43, 166.9.22.51, 166.9.22.52, 166.9.22.8, 166.9.22.9, 166.9.24.19, 166.9.24.196, 166.9.24.198, 166.9.24.22, 166.9.24.35, 166.9.24.4, 166.9.24.45, 166.9.24.47, 166.9.24.5, 166.9.24.90, 166.9.68.130, 166.9.68.134, 166.9.68.34, 166.9.68.47, 166.9.231.217, 166.9.232.15, 166.9.251.118
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T20:54:52Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:582a8f65-9a2b-a072-4fc3-e69ff3462c23",
"description": "Extended description for my secret.",
"expiration_date": "2030-04-01T09:30:00Z",
"id": "582a8f65-9a2b-a072-4fc3-e69ff3462c23",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2020-12-16T20:54:52Z",
"name": "test-arbitrary-secret",
"secret_data": {
"payload": "secret-data"
},
"secret_type": "arbitrary",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T20:54:52Z",
"lease_id": "",
"lease_duration": 0,
"renewable": false,
"data": {
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2020-10-20T16:55:41Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/791f5fb10986423e97aa8512f18b7e65:e415e570-f073-423a-abdc-55de9b58f54e:secret:71539dff-9e84-804a-debb-ab3eb3d8afce",
"id": "71539dff-9e84-804a-debb-ab3eb3d8afce",
"labels": [],
"last_update_date": "2020-10-20T16:55:41Z",
"name": "my-test-arbitrary-secret",
"secret_data": {
"payload": "This is the data for my secret."
},
"secret_type": "ARBITRARY",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2020-10-20T16:55:41Z",
"id": "cc2c795e-0072-8074-9824-b6efd5050232"
}
]
},
"warnings": null
}







 Update a secret
Because cross organizational [gossip](https://hyperledger-fabric.readthedocs.io/en/release-2.2/gossip.html) must be enabled for private data to work, an anchor peer must exist for each organization in the collection definition. Refer to this information for [how to configure anchor peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-channels-anchor-peers) on your network.



Your channel is now configured to use private data.
"serial_number": "fc:22:29:7e:57:25:8a:05",
"state": 1,
"state_description": "Active",
"validity": {
"not_after": "2021-06-04T15:25:44Z",
"not_before": "2021-06-03T15:25:44Z"
},
"versions": [
{
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2021-06-03T22:41:56.354781389Z",
"expiration_date": "2021-06-04T15:25:44Z",
"id": "2fae17bf-106a-1c31-55d9-e642ee3803ae",
"serial_number": "fc:22:29:7e:57:25:8a:05",
"validity": {
"not_after": "2021-06-04T15:25:44Z",
"not_before": "2021-06-03T15:25:44Z"
}
}
]
},
"warnings": null
}

The command to order a public_cert secret returns the following output:

{
"request_id": "64824dec-c53e-8e49-dbe7-6c44c0dcd7a0",
"lease_id": "",
"lease_duration": 0,
"renewable": false,
"data": {
"alt_names": [],
"common_name": "example.com",
"crn": "crn:v1:bluemix:public:kms:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:12e8c9c2-a162-472d-b7d6-8b9a86b815a6:key:02fd6835-6001-4482-a892-13bd2085f75d",
"imported": false,
"creationDate": "2020-03-12T03:37:32Z",
"createdBy": "...",
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"algorithmBitSize": 256,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-12T03:37:32Z",
"keyVersion": {
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"creationDate": "2020-03-12T03:37:32Z"
},
"dualAuthDelete": {
"enabled": false
},
"deleted": false
}
]
}







 Granting access to a key ring 

You can grant access to a key ring within a Key Protect instance by using the IBM Cloud console, [IAM API](https://cloud.ibm.com/apidocs/iam-policy-managementcreate-policy), or [CLI](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_user_policy_create){ :external}.
Sao Paulo (br-sao) api.private.br-sao.logging.cloud.ibm.com 166.9.83.24 <br>166.9.82.23 <br>166.9.84.25<br><br>166.9.83.12 () <br>166.9.82.12 () <br>166.9.84.12 () TCP 443 <br>TCP 80 
 Sydney (au-syd) api.private.au-syd.logging.cloud.ibm.com 166.9.56.3 <br>166.9.52.2 <br>166.9.54.128<br><br>166.9.56.79 () <br>166.9.52.82 () <br>166.9.54.129 () TCP 443 <br>TCP 80 
 Tokyo (jp-tok) api.private.jp-tok.logging.cloud.ibm.com 166.9.40.2 <br>166.9.42.3 <br>166.9.44.13<br><br>166.9.40.13 () <br>166.9.42.72 () <br>166.9.44.76 () TCP 443 <br>TCP 80 
 Toronto (ca-tor) api.private.ca-tor.logging.cloud.ibm.com 166.9.77.23 <br>166.9.76.26 <br>166.9.78.24<br><br>166.9.78.10 () <br>166.9.76.10 () <br>166.9.77.10 () TCP 443 <br>TCP 80 
 Washington (us-east) api.private.us-east.logging.cloud.ibm.com 166.9.22.35 <br>166.9.20.72 <br>166.9.24.247<br><br>166.9.24.171 () <br>166.9.22.194 () <br>166.9.68.157 () TCP 443 <br>TCP 80
List all access policies for a specified trusted profile

ibmcloud iam trusted-profile-policies (NAME|ID) [--output FORMAT] [-f, --force] [-q, --quiet] [--api-version v1 | v2]



 Command options 

NAME|ID (required)
: Name or ID of the profile.

-f, --force
: Force failure if multiple profiles are found.

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-q, --quiet
: Suppress verbose output.

--api-version
: Version of the access policy API.





 Examples 

List all policies of trusted profile ID Profile-bdf62c30-35dd-4852-bcb8-2f0dd3929701:

ibmcloud iam trusted-profile-policies Profile-bdf62c30-35dd-4852-bcb8-2f0dd3929701







 ibmcloud iam trusted-profile-policy-update 

Update an access policy for a trusted profile

ibmcloud iam trusted-profile-policy-update (NAME|ID) POLICY_ID {--file JSON_FILE | -r, --roles ROLE_NAME1,ROLE_NAME2... [--service-name SERVICE_NAME] [--service-instance SERVICE_INSTANCE_GUID] [--region REGION] [--resource-type RESOURCE_TYPE] [--resource RESOURCE] [--resource-group-name RESOURCE_GROUP_NAME] [--resource-group-id RESOURCE_GROUP_ID] [--tags name1:value1,name2:value2...] [--account-management] [--attributes name=value,name=value...]} [--output FORMAT] [-q, --quiet] [-f, --force] [--api-version v1 | v2]



 Command options 

NAME|ID (required)
: Name or ID of the profile to assign the new policy to update.

POLICY_ID (required)
Frankfurt (eu-de) logs.private.eu-de.logging.cloud.ibm.com 166.9.28.3 <br>166.9.32.21 <br>166.9.30.238<br><br>166.9.30.45 () <br>166.9.28.159 () <br>166.9.32.117 () TCP 443 <br>TCP 80 
 London (eu-gb) logs.private.eu-gb.logging.cloud.ibm.com 166.9.36.3 <br>166.9.34.4 <br>166.9.38.5<br><br>166.9.36.105 () <br>166.9.34.79 () <br>166.9.38.84 () TCP 443 <br>TCP 80 
 Osaka (jp-osa) logs.private.jp-osa.logging.cloud.ibm.com 166.9.71.20 <br>166.9.70.21 <br>166.9.72.21<br><br>166.9.71.14 () <br>166.9.72.13 () <br>166.9.70.13 () TCP 443 <br>TCP 80 
 Sao Paulo (br-sao) logs.private.br-sao.logging.cloud.ibm.com 166.9.83.25 <br>166.9.84.27 <br>166.9.82.25<br><br>166.9.83.12 () <br>166.9.82.12 () <br>166.9.84.12 () TCP 443 <br>TCP 80 
 Sydney (au-syd) logs.private.au-syd.logging.cloud.ibm.com 166.9.52.5 <br>166.9.56.20 <br>166.9.54.127<br><br>166.9.56.79 () <br>166.9.52.82 () <br>166.9.54.129 () TCP 443 <br>TCP 80
"address": "192.0.2.0",
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/35984145-9c3a-4626-8ee7-52c7a8742752/reserved_ips/0716-6fd4925d-7774-4e87-829e-7e5765d454ad",
"id": "0716-6fd4925d-7774-4e87-829e-7e5765d454ad",
"name": "my-reserved-ip",
"resource_type": "subnet_reserved_ip"
},
"resource_type": "share_mount_target",
"security_groups":
{
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/security_groups/r134-1dfeccef-3ad6-4760-8653-a202bc795db4",
"id": "r134-1dfeccef-3ad6-4760-8653-a202bc795db4",
"name": "my-security-group",
"resource_type": "security_group"
}
],
"subnet": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/35984145-9c3a-4626-8ee7-52c7a8742752",
"id": "35984145-9c3a-4626-8ee7-52c7a8742752",
"name": "my-subnet",