Skip to content

Commit f6c21c7

Browse files
jmmargojmmargo
authored
Merge pull request #18481 from annawenger20/master
Automatic commit: Move 'cp-sapcp-getstarted' from QA to Production
2 parents a345be8 + bda1985 commit f6c21c7

1 file changed

Lines changed: 13 additions & 21 deletions

File tree

‎tutorials/cp-sapcp-getstarted/cp-sapcp-getstarted.md‎

Lines changed: 13 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ keywords: btp, btp cli, btpcli, command line, command line interface, command li
99
---
1010

1111
## Prerequisites
12-
- You have access to a trial account on SAP BTP
13-
- You are familiar with [the basic concepts of SAP BTP, Trial](cp-trial-quick-onboarding)
12+
- You have access to a global account on SAP BTP that is on feature set B. See [Get an Account on SAP BTP to Try Out Free Tier Service Plans](btp-free-tier-account).
13+
- You are familiar with [the basic concepts of SAP BTP](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/73beb06e127f4e47b849aa95344aabe1.html).
1414

1515
## Details
1616
### You will learn
@@ -22,8 +22,6 @@ keywords: btp, btp cli, btpcli, command line, command line interface, command li
2222
- How to get help in the btp CLI
2323
- Where to find documentation
2424

25-
>With the release of the btp CLI client version 2.0 on March 25, 2021, the executable file name was changed from `sapcp` to `btp`. This change is reflected in all documentation, including this tutorial. If you still have a 1.X version of sapcp CLI, see [Migrating from sapcp to btp](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/4f1fe8dd2739467cb7bcab63f918b8dc.html).
26-
2725
---
2826

2927
[ACCORDION-BEGIN [Step 1: ](What is the btp CLI?)]
@@ -38,25 +36,31 @@ Here are some of the tasks you can use the btp CLI for:
3836
- Managing entitlements of global accounts and subaccounts
3937
- Managing users and their authorizations in global accounts and subaccounts
4038
- Subscribing to applications
39+
- Consuming services that are decoupled from the existing environments (referred to as "Other" environment in the Discovery Center), see [Consuming Services in Other Environments Using SAP Service Manager](https://help.sap.com/docs/SERVICEMANAGEMENT/09cc82baadc542a688176dce601398de/0714ac254e83492281d95e25548b388c.html)
40+
4141

4242
[DONE]
4343
[ACCORDION-END]
4444

4545

4646
[ACCORDION-BEGIN [Step 2: ](For which global accounts can I use the btp CLI?)]
4747

48-
SAP is currently migrating all global accounts from the existing cloud management tools feature set A to the renovated cloud management tools feature set B. One of the innovations of feature set B is the command line interface (btp CLI) for account management. With a trial account, you can try out the btp CLI and other features of feature set B.
48+
SAP is currently migrating all global accounts from the existing cloud management tools feature set A to the renovated cloud management tools feature set B. One of the innovations of feature set B is the command line interface (btp CLI) for account management.
4949

5050
Here you can read more about the [Cloud Management Tools Feature Set B Innovations](https://help.sap.com/viewer/3504ec5ef16548778610c7e89cc0eac3/Cloud/en-US/caf4e4e23aef4666ad8f125af393dfb2.html).
5151

5252

5353
[DONE]
5454
[ACCORDION-END]
5555

56-
[ACCORDION-BEGIN [Step 3: ](btp CLI and cf CLI - What's the difference?)]
56+
[ACCORDION-BEGIN [Step 3: ](btp CLI vs environment-specific CLIs)]
57+
58+
Cloud Foundry: You may have worked with the [Cloud Foundry CLI (cf CLI)](cp-cf-download-cli) to manage your Cloud Foundry environment. To avoid confusion, here's how the **btp CLI** relates to the **cf CLI**:
59+
The btp CLI is the CLI for working with global accounts on SAP BTP. You use the btp CLI for all tasks on global account, directory, and subaccount level. Going down the account hierarchy, the last step with btp CLI is creating a Cloud Foundry environment instance, which essentially creates a Cloud Foundry org. From org level onwards, i.e. for managing service instances and members in orgs and spaces, creating spaces, as well as assigning quota to orgs and spaces, you need to use the cf CLI.
60+
61+
Kyma: The same goes for Kyma: You use the btp CLI for all tasks on global account, directory, and subaccount level. The last step in the btp CLI is create a Kyma environment instance, aka a Kyma cluster. You then need to download the configuration file that you need to access your Kyma cluster. To work in the cluster and manage your Kyma service instances, you need the kubectl. See [Creating SAP BTP, Kyma runtime via the btp CLI](https://blogs.sap.com/2022/02/24/creating-sap-btp-kyma-runtime-via-the-sap-btp-cli/) and [Accessing a Kyma Instance Using kubectl](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/3e25944e491049b2aeec68c562a5ee48.html).
5762

58-
You may have worked with the [Cloud Foundry CLI (cf CLI)](cp-cf-download-cli) to manage your Cloud Foundry environment. To avoid confusion, here's how the **btp CLI** relates to the **cf CLI**:
59-
The btp CLI is the CLI for working with global accounts on SAP BTP. You use the btp CLI for all tasks on global account, directory, and subaccount level. Going down the account hierarchy, the last step with btp CLI is creating a Cloud Foundry environment instance, which essentially creates a Cloud Foundry org. From org level onwards, i.e. for managing members in orgs and spaces, creating spaces, as well as assigning quota to orgs and spaces, you use the cf CLI.
63+
"Other" Environments: SAP Service Manager allows you to consume services from any runtime environment directly from the subaccount. We refer to this as "other" environment. For this environment type "other", you can use the btp CLI to manage services, instances, plans, and the like, because these are managed on subaccount level. See [Working With Resources of SAP Service Manager Using the btp CLI](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/fe6a53bfe48e4831b2f5ae7f06d4f07d.html).
6064

6165
[VALIDATE_1]
6266
[ACCORDION-END]
@@ -145,18 +149,12 @@ Once you're logged into your global account, it should look similar to this:
145149
[DONE]
146150
[ACCORDION-END]
147151

148-
[ACCORDION-BEGIN [Step 6: ](Understand the command syntax: usage)]
152+
[ACCORDION-BEGIN [Step 6: ](Understand the command syntax)]
149153

150154
![CLI command syntax](usage.png)
151155

152156
Each command starts with the base call `btp`. The syntax of the command itself is very close to natural language: It starts with a verb, i.e. the *action*, followed by a *group/object* combination. So you build a command by combining `btp` with an action (let's say *list*) and a group/object combination (let's say *accounts/subaccount*): `btp list accounts/subaccount`
153157

154-
155-
[DONE]
156-
[ACCORDION-END]
157-
158-
[ACCORDION-BEGIN [Step 7: ](Understand the command syntax: options)]
159-
160158
Additionally, **options** and **parameters** can be added to a command. As you've seen in the overview of all commands, there are the following options that you can add at the beginning of each command. For example, to use the verbose mode.
161159

162160
```Bash
@@ -167,12 +165,6 @@ btp --verbose list accounts/subaccount
167165

168166
>To call help, you can always place `--help` at the end of a command, even if it's not complete. For example, `btp list --help`, `btp accounts --help`.
169167
170-
[DONE]
171-
[ACCORDION-END]
172-
173-
174-
[ACCORDION-BEGIN [Step 8: ](Understand the command syntax: parameters)]
175-
176168
**Parameters** are added to the end, after the group/object combination. A command can have one **positional parameter** as the first one, followed by other optional or mandatory parameters. The positional parameter is used without a key, all others have a key. The command help specifies the optionality of all parameters and describes what you can or have to add.
177169

178170
For example:

0 commit comments

Comments
 (0)