vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* VMware Site Recovery Manager
* VMware Aria Automation Enterprise
* VMware Aria Operation Enterprise
* VMware Aria Operations for Logs



Small differences exist between NSX-T Data Center and Data Center SP editions. For more information, see [Product offerings for VMware NSX-T Data Center 3.2.x](https://kb.vmware.com/s/article/86095).





 Licensing options 

Using individual license keys together with the combined license keys does not meet the payment requirements for the licenses you need.

You have the following options for licensing the selected VMware components:



* Include license with purchase: In this case, a new license for the VMware component is purchased on your behalf. A combined VMware license is generated to match the cluster size of the order.

When you purchase any license, except for vSphere Enterprise Plus and vCenter Server, and you order multiple VMware ESXi™ servers, an IBM Cloud ticket is opened automatically to combine license keys. You are responsible to follow up with the ticket to ensure that you use only the license keys that the VMware Solutions Support team generates.
* I will provide the license: Bring your own license (BYOL) is no longer allowed for VMware components except if you are migrating or upgrading an existing BYOL cluster. If you are upgrading your cluster, do not enter your BYOL licenses when you create your order for the first time, but do it later when the vSphere instance is created.







 Related links 



* [Bare metal server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_orderinginstances-bare-metal-settings)
* [Procedure to order VMware vSphere instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_orderinginstances-procedure)
[(2036943312, 33.7631862, -84.3939405),
(3523447568, 33.7632666, -84.3939315),
(2036943524, 33.7633273, -84.3939155)]
4. Find the best route with minimal distance cost (the fastest route distance-wise):

>>> best_distance_route = router.compute_route(start, end, method='distance')
 Check distance cost, in the unit of meters
>>> best_distance_route.cost
2042,4082601271236
 Check route path (only showing the first three points), which is a list of points in 3-tuple (osm_point_id, lat, lon)
>>> best_distance_route.path[:3]
[(2036943312, 33.7631862, -84.3939405),
(3523447568, 33.7632666, -84.3939315),
(2036943524, 33.7633273, -84.3939155)]
: UUID for the load balancer policy.

-t, --type TYPE (required)
: Rule type: HOST_NAME | FILE_TYPE | HEADER | COOKIE | PATH

-c, --compare-type COMPARE_TYPE (required)
: Compare type: EQUAL_TO | ENDS_WITH | STARTS_WITH | REGEX | CONTAINS

-v, --value COMPARE_VALUE (required)
: Compared value.

-k, --key KEY
: Key name. Available only in HEADER or COOKIE type.

--invert VALUE
: Invert rule: 0 | 1







 ibmcloud sl loadbal l7rule-delete 

Delete an L7 rule:

ibmcloud sl loadbal l7rule-delete (--policy-uuid L7POLICY_UUID) (--rule-uuid L7RULE_UUID) [-f, --force]



 Command options 

--policy-uuid UUID (required)
: UUID for the load balancer policy.

--rule-uuid UUID (required)
: UUID for the load balancer rule.

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





 Examples 

ibmcloud sl loadbal l7rule-delete --policy-uuid 27204f2c-1853-4fd2-9c97-1654cd536edd --rule-uuid 27204f2c-1853-4fd2-9c97-1654cd536edd -f







 ibmcloud sl loadbal l7rules 

List L7 rules:

ibmcloud sl loadbal l7rules (--policy-id Policy_ID)



 Command options 

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





 Examples 

ibmcloud sl loadbal l7rules --policy-id 27204f2c-1853-4fd2-9c97-1654cd536edd
}





 The $gt operator 

The $gt operator matches if the specified field content is greater than the argument.

See the following example that uses the $gt operator with full-text indexing:

{
"selector": {
"year": {
"$gt": 2001
}
},
"sort": [
"year:number",
"title:string"
],
"fields": [
"year",
"title"
]
}

See the following example that uses the $gt operator with a database that is indexed on the field year:

{
"selector": {
"year": {
"$gt": 2001
}
},
"sort": [
"year"
],
"fields": [
"year"
]
}





 The $exists operator 

The $exists operator matches if the field exists, no matter what its value is.

See the following example that uses the $exists operator:

{
"selector": {
"year": 2015,
"title": {
"$exists": true
}
},
"fields": [
"year",
"_id",
"title"
]
}





 The $type operator 

The $type operator requires that the specified document field is of the correct type.

See the following example that uses the $type operator:

{
"selector": {
"year": {
"$type": "number"
}
},
"fields": [
"year",
"_id",
"title"
]
}





 The $in operator 

The $in operator requires that the document field must exist in the list provided.

See the following example that uses the $in operator:

{
"selector": {
"year": {
"$in": [2010, 2015]
}
},
"fields": [
CompanyShareholder 
 Competition 
 CompetitiveSpace 
 Composer 
 Composition 
 CompositionalForm 
 ComputerPeripheral 
 ComputingPlatform 
 ConcertFilm 
 ConcertTour 
 ConductedEnsemble 
 Conductor 
 Conference 
 ConferenceSeries 
 ConsumerProduct 
 ContentLicense 
 Continent 
 Country 
 CranialNerve 
 CreativeWork 
 CricketAdministrativeBody 
 CricketTournamentEvent 
 Criminal 
 CriminalOffense 
 Cuisine 
 CulinaryMeasure 
 CulinaryTool 
 DedicatedWork 
 Dedicatee 
 Dedicator 
 Degree 
 Deity 
 DietFollower 
 DigitalCamera 
 DisasterSurvivor 
 Disease 
 DiseaseCause 
 DiseaseOrMedicalCondition 
 Dish 
 DomesticatedAnimal 
 DrinkingEstablishment 
 Drug 
 Election 
 ElectionCampaign 
 EndorsedProduct 
 Engine 
 Facility 
 Family 
 FamilyName 
 FashionLabel 
 FictionalCreature 
 FictionalJobTitle 
 FictionalUniverse 
 FictionalUniverseCreator 
 FieldOfStudy 
 FileFormat 
 Film 
 FilmActor 
 FilmCharacter 
 FilmCinematographer 
 FilmCompany 
 FilmCritic 
 FilmDirector 
 FilmDistributor 
 FilmEditor 
 FilmFestival 
 FilmFestivalEvent 
 FilmFestivalFocus 
 FilmJob 
 FilmMusicContributor 
 FilmProducer 
 FilmSeries 
 FilmWriter 
 FootballCompetition 
 FootballDivision 
 FootballLeague 
 FootballManager 
 FootballMatch 
 FootballOrganization 
 FootballPlayer 
 FootballPosition 
 FootballTeam 
 FootballWorldCup 
 Galaxy 
 Game 
 GameDesigner 
 GameExpansion 
 GamePublisher 
 GeneralElection 
 GeographicFeature 
 GovernmentAgency 
 GovernmentalBody 
 GovernmentOfficeOrTitle 
 Governor 
 Guitar 
 Guitarist 
 HallOfFame 
 HallOfFameInductee 
 HistoricPlace 
 Hobby 
 HockeyCoach 
 HockeyConference 
 HockeyDivision
Only PublicToPrivate and PrivateToPrivate load balancer types are accepted.

-l, --label LABEL
: A descriptive label for this load balancer.

--frontend-protocol PROTOCOL
: Frontend protocol. Default: HTTP

--frontend-port PORT
: Frontend port. Default: 80

-m, --method METHOD
: Balancing method. Accepted values are ROUNDROBIN | LEASTCONNECTION | WEIGHTED_RR. Default: ROUNDROBIN

-c, --connections COUNT
: Maximum number of connections.

--sticky METHOD<
: Sticky session method: cookie or source-ip.

--use-public-subnet
: If this option is specified, the public IP is allocated from a public subnet in this account. Otherwise, it is allocated from the IBM system pool. Only available in PublicToPrivate load balancer type.

--verify
: Verify an order, but do not create it.

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





 Examples 

ibmcloud sl loadbal order -n my-lb -d DALLAS10 -t PublicToPrivate -s 1234567 --frontend-protocol TCP --frontend-port 123 --backend-protocol TCP --backend-port 123 -m LEASTCONNECTION -c 100 --sticky cookie







 ibmcloud sl loadbal order-options 

List options for order a load balancer:

ibmcloud sl loadbal order-options [-d, --datacenter DATACENTER]



 Command options 

-d, --datacenter NAME
: Show only the selected data center. Use shortname (dal13) format.





 Examples 

ibmcloud sl loadbal order-options







 ibmcloud sl loadbal protocol-add 

Add a load balancer protocol:
"row_header_ids" : "rowHeader-2244-2262" ],
"row_header_texts" : "Statutory tax rate" ],
"row_header_texts_normalized" : "Statutory tax rate" ],
"column_header_ids" : "colHeader-1050-1082", "colHeader-1544-1548" ],
"column_header_texts" : "Three months ended September 30,", "2005" ],
"column_header_texts_normalized" : "Three months ended September 30,", "Year 1" ],
"attributes": ]
}, {
"cell_id" : "bodyCell-2633-2638",
"location" : {
"begin" : 2633,
"end" : 2639
},
"text" : "35.0%",
"row_index_begin" : 2,
"row_index_end" : 2,
"column_index_begin" : 2,
"column_index_end" : 2,
"row_header_ids" : "rowHeader-2244-2262" ],
"row_header_texts" : "Statutory tax rate" ],
"row_header_texts_normalized" : "Statutory tax rate" ],
"column_header_ids" : "colHeader-1050-1082", "colHeader-1712-1716" ],
"column_header_texts" : "Three months ended September 30,", "2004" ],
"column_header_texts_normalized" : "Three months ended September 30,", "Year 2" ],
"attributes": ]
}, {
"cell_id" : "bodyCell-2825-2830",
"location" : {
"begin" : 2825,
"end" : 2831
},
"text" : "35.0%",
"row_index_begin" : 2,
The following table describes each possible method, why you might use it, and how to set it up. For basic information about the networking services that are listed, see [Understanding Kubernetes service types](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_network_planningexternal).

You can't use multiple app exposure methods for one app.



Characteristics of public app exposure methods

 Name Load-balancing method Use case Implementation 

 Route HTTP(S) load balancing that exposes the app with a subdomain and uses custom routing rules Implement custom routing rules and SSL termination for multiple apps. Choose this method to remain Red Hat OpenShift-native; for example, you can use the Red Hat OpenShift web console to create and manage routes.<br><br><br><br>1. [Create a ClusterIP service](https://kubernetes.io/docs/concepts/services-networking/service/defining-a-service) to assign an internal IP address to your app.<br>2. [Set up a Red Hat OpenShift route](https://docs.openshift.com/container-platform/4.11/applications/deployments/route-based-deployment-strategies.html).<br>3. Customize routing rules with [optional configurations](https://docs.openshift.com/container-platform/4.11/networking/routes/route-configuration.html).<br><br><br> 
 NodePort Port on a worker node that exposes the app on the worker's public IP address Test public access to one app or provide access for only a short amount of time. [Create a public NodePort service](https://cloud.ibm.com/docs/openshift?topic=openshift-nodeportnodeport_config). 
 NLB v1.0 (+ subdomain) Basic load balancing that exposes the app with an IP address or a subdomain. Quickly expose one app to the public with an IP address or a subdomain that supports SSL termination.
Frankfurt eu-de fra02 158.177.186.255/24 158.177.186.1 
 Frankfurt eu-de fra02 158.177.187.255/24 158.177.187.1 
 Frankfurt eu-de fra02 158.177.241.255/24 158.177.241.1 
 Frankfurt eu-de fra02 158.177.110.111/29 158.177.110.105 
 Frankfurt eu-de fra02 158.177.221.175/29 158.177.221.169 
 Frankfurt eu-de fra02 159.122.89.23/29 159.122.89.17 
 Frankfurt eu-de fra02 159.122.97.23/29 159.122.97.17 
 Frankfurt eu-de fra02 159.122.97.47/29 159.122.97.41 
 Frankfurt eu-de fra02 159.122.108.215/29 159.122.108.209 
 Frankfurt eu-de fra02 159.122.108.223/29 159.122.108.217 
 Frankfurt eu-de fra02 169.50.10.15/29 169.50.10.9 
 Frankfurt eu-de fra02 169.50.13.207/29 169.50.13.201 
 Frankfurt eu-de fra02 169.50.15.31/29 169.50.15.25 
 Frankfurt eu-de fra02 169.50.15.191/29 169.50.15.185 
 Frankfurt eu-de fra02 169.50.25.231/29 169.50.25.225 
 Frankfurt eu-de fra02 169.50.35.111/29 169.50.35.105 
 Frankfurt eu-de fra02 169.50.35.239/29 169.50.35.233 
 Frankfurt eu-de fra02 169.50.53.247/29 169.50.53.241 
 Frankfurt eu-de fra02 169.50.54.23/29 169.50.54.17 
 Frankfurt eu-de fra04 161.156.2.255/24 161.156.2.1
tok02 BCR02 10.212.0.0/16 <br>10.44.0.0/16 
 tok04 BCR01 10.3.17.0/24 <br>10.192.0.0/16 <br>10.201.187.0/24 
 tok05 BCR01 10.3.19.0/24 <br>10.193.0.0/16 <br>10.201.203.0/24 
 tor01 BCR01 10.2.59.0/24 <br>10.3.42.0/24 <br>10.114.0.0/15 <br>10.202.107.0/24 
 tor01 BCR02 10.166.0.0/15 
 tor04 BCR01 10.1.2.0/24 <br>10.3.53.0/24 <br>10.11.0.0/16 
 tor05 BCR01 10.1.6.0/24 <br>10.3.51.0/24 <br>10.243.0.0/16 
 Washington D.C. wdc01 BCR05 10.108.0.0/15 
 wdc01 BCR06 10.124.0.0/15 
 wdc04 BCR01 10.3.10.0/29 <br>10.3.52.0/24 <br>10.3.171.0/24 <br>10.3.240.0/24 <br>10.148.0.0/15 
 wdc04 BCR02 10.0.192.128/26 <br>10.170.0.0/16 
 wdc04 BCR03 10.183.0.0/16 <br>10.216.0.0/16 
 wdc04 BCR04 10.65.0.0/16 <br>10.201.11.0/24 <br>10.211.0.0/16 
 wdc04 BCR05 10.213.0.0/16
AP: Sydney Public (Tethered) s3.syd.ap.cloud-object-storage.appdomain.cloud 
 AP: Osaka Public (Tethered) s3.osa.ap.cloud-object-storage.appdomain.cloud 







 Tethered endpoint reference 

Public

Private

Direct



Table 2. Cross Region Static Web Endpoints

 Region Hosted Static Website Endpoint 

 US: Dallas s3-web.dal.us.cloud-object-storage.appdomain.cloud 
 US: San Jose s3-web.sjc.us.cloud-object-storage.appdomain.cloud 
 US: Washington, D.C. s3-web.wdc.us.cloud-object-storage.appdomain.cloud 
 EU: Amsterdam s3-web.ams.eu.cloud-object-storage.appdomain.cloud 
 EU: Frankfurt s3-web.fra.eu.cloud-object-storage.appdomain.cloud 
 EU: Milan s3-web.mil.eu.cloud-object-storage.appdomain.cloud 
 AP: Tokyo s3-web.tok.ap.cloud-object-storage.appdomain.cloud 
 AP: Sydney s3-web.syd.ap.cloud-object-storage.appdomain.cloud 
 AP: Osaka s3-web.osa.ap.cloud-object-storage.appdomain.cloud 







 Next Steps 

Different services and the features they support may vary region by region. Check the documentation for more information regarding [service availability](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-availability).
0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-
location The location of the termination date as defined by its begin and end indexes. 
 provenance_ids An array of hashed values that you can send to IBM to provide feedback or receive support. 







 Contract types 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The contract_types array identifies the document's contract type or types as declared in the document.



 contract_types Description 

 confidence_level The confidence level of the identification of the contract type. Possible values include High, Medium, and Low. 
 text The contract type, listed as a string. 
 location The location of the contract type as defined by its begin and end indexes. 
 provenance_ids An array of hashed values that you can send to IBM to provide feedback or receive support. 







 Contract terms 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The contract_terms array identifies the duration or durations of the contract as declared in the document.



 contract_terms Description 

 confidence_level The confidence level of the identification of the contract term. Possible values include High, Medium, and Low. 
 text The contract term, listed as a string. 
 location The location of the contract term as defined by its begin and end indexes. 
 provenance_ids An array of hashed values that you can send to IBM to provide feedback or receive support. 







 Payment terms 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The payment_terms array identifies the payment duration or durations as declared in the document.



 payment_terms Description 

 confidence_level The confidence level of the identification of the payment term. Possible values include High, Medium, and Low. 
 text The payment term, listed as a string. 
 normalized_text The normalized text, if applicable. 
 interpretation The details of the normalized text, if applicable. 
 value A string listing the value that was found in the normalized text. 
 numeric_value An integer or float expressing the numeric value of the value key. 
 unit A string listing the unit of the value that was found in the normalized text.
* The default route for internet traffic (used when a public gateway or floating IP is associated with the VPC)
* Routes to the classic infrastructure service network CIDRs (used when a service gateway is associated with the VPC), for example:

10.0.0.0/14, 10.200.0.0/14, 10.198.0.0/15, and 10.254.0.0/16 are classic infrastructure service network CIDRs.







 Determining route preference 

You can designate the route priority (0-4) of VPC routes to determine which routes have a higher priority when there are multiple routes for a given destination. Existing routes and new routes, created without a priority value, are automatically set to the default priority (2).

The route priority is considered on identical destinations only and is similar to any dynamically learned route.



 Setting route priority examples 



* If you have a route with a /32 prefix and priority of 1, and a route with destination of /31 and priority 0, then /32 is used first (longest prefix match). In other words, priority matters only when there is more than one route with the exact same prefix.
* If you have three routes with 0.0.0.0/0 (default route), only the route with the highest priority is used. If the selected route is removed (for example, through automation), the highest priority from the remaining two routes is selected.
* If there is only one route with a given prefix in the custom routing table, that one route is always used regardless of its priority. Best route selection is performed for every given prefix and picks the route with the highest priority.



Equal-Cost Multi-Path (ECMP) routing is used when two routes have the same destination and priority (extending the current behavior where ECMP is used for two routes with same destination). At most, two routes in a routing table are allowed to have the same destination and priority. For example, if the custom routing table has three routes with the same destination, one route with priority 1 and the other two routes with priority 4 (ECMP), the route with priority 1 is selected and the ECMP routes are ignored (no ECMP).
0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],-0.007785297930240631,-0.0015305652050301433],
action: keep

- regex: "(__name__)|(job)|(region)|(instance)|(status)|(core)|(name)|(start_mode)|(nic)|(volume)|(state)|(version)|(mode)|(branch)|(timezone)|(goversion)|(collector)|(revision)"
action: labelkeep

Where

ENDPOINT is the monitoring collector endpoint. To see the list of endpoints, see [collector endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_ingestion).

monitoring-apikey is the file that contains the Monitor API Token. Notice that the file name does not have an extension. For more information about how to get the API token, see [Working with Monitor API tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-api_monitoring_token).

For example, the completed version of the prometheus.yml could look like :

 my global config
global:
scrape_interval: 15s Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s Evaluate rules every 15 seconds. The default is every 1 minute.
 scrape_timeout is set to the global default (10s).

 Alertmanager configuration
alerting:
alertmanagers:
- static_configs:
- targets:
 - alertmanager:9093

 Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
 - "first_rules.yml"
 - "second_rules.yml"

 A scrape configuration containing exactly one endpoint to scrape:
 Here it's Prometheus itself.
scrape_configs:
 The job name is added as a label job=<job_name> to any timeseries scraped from this config.
- job_name: 'windows_exporter'

static_configs:
"column_header_texts_normalized" : "Three months ended September 30,", "Year 2" ],
"attributes": ]
}, {
"cell_id" : "bodyCell-2825-2830",
"location" : {
"begin" : 2825,
"end" : 2831
},
"text" : "35.0%",
"row_index_begin" : 2,
"row_index_end" : 2,
"column_index_begin" : 3,
"column_index_end" : 3,
"row_header_ids" : "rowHeader-2244-2262" ],
"row_header_texts" : "Statutory tax rate" ],
"row_header_texts_normalized" : "Statutory tax rate" ],
"column_header_ids" : "colHeader-1270-1301", "colHeader-1889-1893" ],
"column_header_texts" : "Nine months ended September 30,", "2005" ],
"column_header_texts_normalized" : "Nine months ended September 30,", "Year 1" ],
"attributes": ]
}, {
"cell_id" : "bodyCell-3008-3013",
"location" : {
"begin" : 3008,
"end" : 3014
},
"text" : "35.0%",
"row_index_begin" : 2,
"row_index_end" : 2,
"column_index_begin" : 4,
"column_index_end" : 4,
"row_header_ids" : "rowHeader-2244-2262" ],
"row_header_texts" : "Statutory tax rate" ],
"row_header_texts_normalized" : "Statutory tax rate" ],
For more information about available command options, see [ibmcloud is backup-policy-plan](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-plan).







 Viewing backup policies and plans with the API 

You can view backup policies and plans by using the API.



 Showing details of a backup policy with the API 

Make a GET /backup_policies/{backup_policy_id} request to show details of a backup policy that is identified by ID.

curl -X GET "$vpc_api_endpoint/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f?version=2022-06-03&generation=2" -H "Authorization: $iam_token"

A successful response looks like the following example.

{
"created_at": "2022-06-06T23:29:55.833Z",
"crn": "crn:v1:bluemix:public:is:us-south:a/123456::backup-policy:fb721535-2cc6-45d6-ade7-3ceb95b7f26f",
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f",
"id": "fb721535-2cc6-45d6-ade7-3ceb95b7f26f",
"lifecycle_state": "stable",
"match_resource_types": [

"volume"
]
],
"match_user_tags": [
"my-daily-backup-policy"
],
"name": "my-backup-policy",
"plans": [
{
Optionally, you can specify the name of the plan that you want to see. data "ibm_is_backup_policy_plans" "example" {
backup_policy_id = ibm_is_backup_policy.example.id
}
data "ibm_is_backup_policy_plans" "example" {
backup_policy_id = ibm_is_backup_policy.example.id
name = "my-policy-plan"
}
For more information about the arguments and attributes, see ibm_is_backup_policy_plans]ibm_is_backup_policy_plans] ! ! .<-- </section "id="section-backup-view-plans-terraform" "> --><-- <section "id="section-backup-view-plan-details-terraform" "> --> Viewing backup plan details with Terraform Import the details of a backup plan as a read-only data source. You can specify either the plan ID or the plan name as you can see in the following examples. data "ibm_is_backup_policy_plan" "example" {
backup_policy_id = ibm_is_backup_policy.example.id
identifier = ibm_is_backup_policy_plan.example.id
}
data "ibm_is_backup_policy_plan" "example" {
backup_policy_id = ibm_is_backup_policy.example.id
name = ibm_is_backup_policy_plan.example.name
}
For more information about the arguments and attributes, see ibm_is_backup_policy_plan]ibm_is_backup_policy_plan] ! ! ! !