Skip to content

Commit d86d95b

Browse files
author
cfsdocs
committed
Merge pull request #1764 from coligo/fmo-upd-02Feb22-a
1 parent 1f1bcbf commit d86d95b

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

56 files changed

+799
-811
lines changed

Diff for: add-registry.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2022
5-
lastupdated: "2022-01-31"
5+
lastupdated: "2022-02-02"
66

77
keywords: registries, container registry, image registry, apikey, API key, access token, images, registry access, service id
88

@@ -111,7 +111,7 @@ Now that you created your API key, [save it as registry access](#add-registry-ac
111111

112112
To create an {{site.data.keyword.cloud_notm}} IAM API key with the CLI, run the [**`iam api-key-create`**](/docs/account?topic=cli-ibmcloud_commands_iam#ibmcloud_iam_api_key_create) command. For example, to create an API key called `cliapikey` with a description of "My CLI APIkey" and save it to a file called `key_file`, run the following command:
113113

114-
```sh
114+
```txt
115115
ibmcloud iam api-key-create cliapikey -d "My CLI APIkey" --file key_file
116116
```
117117
{: pre}
@@ -177,14 +177,14 @@ To add {{site.data.keyword.registryfull_notm}} or Docker Hub access with the CLI
177177

178178
For example, the following **`registry create`** command creates registry access to an {{site.data.keyword.registryfull_notm}} instance called `myregistry` that is on the `us.icr.io` registry server:
179179

180-
```sh
180+
```txt
181181
ibmcloud ce registry create --name myregistry --server us.icr.io --username iamapikey --password API_KEY
182182
```
183183
{: pre}
184184

185185
**Example output**
186186

187-
```sh
187+
```txt
188188
Creating image registry access secret 'myregistry'...
189189
OK
190190
```
@@ -264,7 +264,7 @@ To pull images from {{site.data.keyword.registryfull_notm}} in a different accou
264264

265265
For example, the following command creates a service ID called `codeengine-myproject-id` with the description `Service ID for IBM Cloud Container Registry in {{site.data.keyword.codeengineshort}} project myproject`:
266266

267-
```sh
267+
```txt
268268
ibmcloud iam service-id-create codeengine-myproject-id --description "Service ID for IBM Cloud Container Registry in {{site.data.keyword.codeengineshort}} project my proj"
269269
```
270270
{: pre}
@@ -273,7 +273,7 @@ To pull images from {{site.data.keyword.registryfull_notm}} in a different accou
273273
274274
For example, the following command creates a policy for `codeengine-myproject-id` service ID with the role of `Reader`:
275275
276-
```sh
276+
```txt
277277
ibmcloud iam service-policy-create codeengine-myproject-id --roles Reader --service-name container-registry
278278
```
279279
{: pre}
@@ -292,7 +292,7 @@ To pull images from {{site.data.keyword.registryfull_notm}} in a different accou
292292
293293
For example, create a policy for `codeengine-myproject-id` service ID with the role of `Operator`:
294294
295-
```sh
295+
```txt
296296
ibmcloud iam service-policy-create codeengine-myproject-id --roles Operator --service-name iam-identity
297297
```
298298
{: pre}
@@ -311,14 +311,14 @@ To pull images from {{site.data.keyword.registryfull_notm}} in a different accou
311311
312312
For example, the following command creates a key called `codeengine-myproject-key` for the `codeengine-myproject-id` service ID with a description of `API key for service ID codeengine-myproject-id for {{site.data.keyword.codeengineshort}} myproject`:
313313
314-
```sh
314+
```txt
315315
ibmcloud iam service-api-key-create codeengine-myproject-key codeengine-myproject-id --description "API key for service ID codeengine-myproject-id for {{site.data.keyword.codeengineshort}} myproject"
316316
```
317317
{: pre}
318318
319319
**Example output**
320320
321-
```sh
321+
```txt
322322
Please preserve the API key! It cannot be retrieved after it's created.
323323
324324
Name codeengine-myproject-key

Diff for: api.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2022
5-
lastupdated: "2022-01-28"
5+
lastupdated: "2022-02-02"
66

77
keywords: api reference, api, Kubernetes configuration and code engine, CRD for code engine, CRD, custom resource definition, guid, kubernetes, authenticate, code engine api
88

@@ -42,14 +42,14 @@ Determine the GUID of your {{site.data.keyword.codeengineshort}} project by quer
4242

4343
1. Log in into {{site.data.keyword.cloud_notm}} and target a region, account, and resource group.
4444

45-
```sh
45+
```txt
4646
ibmcloud login target -r REGION -c ACCOUNT_ID -g RESOURCE_GROUP
4747
```
4848
{: pre}
4949
5050
2. Run the **`ibmcloud resource`** command.
5151
52-
```sh
52+
```txt
5353
ibmcloud resource service-instances --service-name codeengine --long
5454
```
5555
{: pre}
@@ -66,7 +66,7 @@ Before you begin, you must have the `access_token` from the previous step.
6666
6767
**Example output**
6868
69-
```sh
69+
```txt
7070
curl -X GET \
7171
'https://globalcatalog.cloud.ibm.com/api/v1?include=*&q=name:codeengine+active:true' \
7272
-H 'Authorization: Bearer ACCESS_TOKEN'
@@ -79,7 +79,7 @@ Before you begin, you must have the `access_token` from the previous step.
7979
8080
**Example output**
8181
82-
```sh
82+
```txt
8383
curl -X GET \
8484
'https://resource-controller.cloud.ibm.com/v2/resource_instances?name=MY_PROJECT&resource_id=RESOURCE_ID' \
8585
-H 'Authorization: Bearer ACCESS_TOKEN'
@@ -102,7 +102,7 @@ Use the [`get kubeconfig for the specified project`](https://cloud.ibm.com/apido
102102
#### Example output
103103
{: #api-query-example}
104104
105-
```sh
105+
```txt
106106
curl -X GET \
107107
'https://resource-controller.cloud.ibm.com/v2/resource_instances?name=MY_PROJECT&resource_id=RESOURCE_ID' \
108108
-H 'Authorization: Bearer ACCESS_TOKEN'
@@ -114,21 +114,21 @@ curl -X GET \
114114

115115
1. Log in into {{site.data.keyword.cloud_notm}} and target a region, account, and resource group.
116116

117-
```sh
117+
```txt
118118
ibmcloud login target -r REGION -c ACCOUNT_ID -g RESOURCE_GROUP
119119
```
120120
{: pre}
121121
122122
2. Create your {{site.data.keyword.codeengineshort}} project:
123123
124-
```sh
124+
```txt
125125
ibmcloud ce project create --name PROJECT
126126
```
127127
{: pre}
128128
129129
3. Select your {{site.data.keyword.codeengineshort}} project as the current context and append the project to the default Kubernetes configuration file.
130130
131-
```sh
131+
```txt
132132
ibmcloud ce project select --name PROJECT --kubecfg
133133
```
134134
{: pre}

Diff for: app-tutorial.md

+22-22
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2022
5-
lastupdated: "2022-01-28"
5+
lastupdated: "2022-02-02"
66

77
keywords: app tutorial for code engine, application, apps, images, tutorial for code engine, deploying
88

@@ -47,14 +47,14 @@ If you have a container image that you want to use, you can replace the image re
4747

4848
1. Create your application by using the [**`ibmcloud ce application create`**](/docs/codeengine?topic=codeengine-cli#cli-application-create) command. In the following example, use `myapp` as the name of the application and specify `icr.io/codeengine/hello` as the image to reference.
4949

50-
```sh
50+
```txt
5151
ibmcloud ce application create --name myapp --image icr.io/codeengine/hello
5252
```
5353
{: pre}
5454
5555
**Example output**
5656
57-
```sh
57+
```txt
5858
Creating application 'myapp'...
5959
[...]
6060
Run 'C:\Program Files\IBM\Cloud\bin\ibmcloud.exe ce application get -n myapp' to check the application status.
@@ -65,14 +65,14 @@ If you have a container image that you want to use, you can replace the image re
6565
6666
2. Run the [**`ibmcloud ce application get`**](/docs/codeengine?topic=codeengine-cli#cli-application-get) command to display details about the application, including the URL for the `myapp` application.
6767
68-
```sh
68+
```txt
6969
ibmcloud ce application get -n myapp
7070
```
7171
{: pre}
7272
7373
**Example output**
7474
75-
```sh
75+
```txt
7676
Run 'ibmcloud ce application events -n myapp' to get the system events of the application instances.
7777
Run 'ibmcloud ce application logs -f -n myapp' to follow the logs of the application instances.
7878
OK
@@ -126,29 +126,29 @@ If you have a container image that you want to use, you can replace the image re
126126
127127
3. Obtain the URL of the application from running the **`application get`** command as described in the previous step. To retrieve the URL of the application directly, you can use the `--output` option and specify the URL format on the **`application get`** command. Additionally, you can run the [**`ibmcloud ce application list`**](/docs/codeengine?topic=codeengine-cli#cli-application-list) command to get the application URL.
128128
129-
```sh
129+
```txt
130130
ibmcloud ce application get -n myapp -output url
131131
```
132132
{: pre}
133133
134134
**Example output**
135135
136-
```sh
136+
```txt
137137
https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
138138
```
139139
{: screen}
140140
141141
142142
4. Copy the URL from the previous output and call the application with `curl`.
143143
144-
```sh
144+
```txt
145145
curl https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
146146
```
147147
{: pre}
148148
149149
**Example output**
150150
151-
```sh
151+
```txt
152152
Hello World
153153
```
154154
{: screen}
@@ -161,14 +161,14 @@ You successfully deployed and started a {{site.data.keyword.codeengineshort}} ap
161161
162162
1. Update your newly created application by adding an environment variable to return `Hello Stranger` with the [**`ibmcloud ce application update`**](/docs/codeengine?topic=codeengine-cli#cli-application-update) command.
163163
164-
```sh
164+
```txt
165165
ibmcloud ce application update --name myapp --env TARGET=Stranger
166166
```
167167
{: pre}
168168
169169
**Example output**
170170
171-
```sh
171+
```txt
172172
Updating application 'myapp' to latest revision.
173173
[...]
174174
Run 'ibmcloud ce application get -n myapp' to check the application status.
@@ -180,14 +180,14 @@ You successfully deployed and started a {{site.data.keyword.codeengineshort}} ap
180180
181181
2. Use the **`application get`** command to display details about your app, including the latest revision information.
182182
183-
```sh
183+
```txt
184184
ibmcloud ce application get --name myapp
185185
```
186186
{: pre}
187187
188188
**Example output**
189189
190-
```sh
190+
```txt
191191
Run 'ibmcloud ce application events -n myapp' to get the system events of the application instances.
192192
Run 'ibmcloud ce application logs -f -n myapp' to follow the logs of the application instances.
193193
OK
@@ -254,14 +254,14 @@ You successfully deployed and started a {{site.data.keyword.codeengineshort}} ap
254254
255255
3. Call the application.
256256
257-
```sh
257+
```txt
258258
curl https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
259259
```
260260
{: pre}
261261
262262
**Example output**
263263
264-
```sh
264+
```txt
265265
Hello Stranger
266266
```
267267
{: screen}
@@ -278,21 +278,21 @@ The following example illustrates how to scale your application with the CLI. Yo
278278
279279
1. Call the application.
280280
281-
```sh
281+
```txt
282282
curl https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
283283
```
284284
{: pre}
285285
286286
2. Run the **`application get`** command to display the status of your application. Notice the value for `Running instances`. In this example, the app has `1` running instance.
287287
288-
```sh
288+
```txt
289289
ibmcloud ce application get -name myapp
290290
```
291291
{: pre}
292292
293293
**Example output**
294294
295-
```sh
295+
```txt
296296
[...]
297297
298298
Name: myapp
@@ -344,14 +344,14 @@ The following example illustrates how to scale your application with the CLI. Yo
344344
345345
3. Run the **`application get`** command again and notice that the value for `Running instances` scaled to zero. When the application is finished running, the number of running instances automatically scales to zero, if the `--min-scale` option is set to `0`, which is the default value.
346346
347-
```sh
347+
```txt
348348
ibmcloud ce application get -n myapp
349349
```
350350
{: pre}
351351
352352
**Example output**
353353
354-
```sh
354+
```txt
355355
[...]
356356
URL: https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
357357
Cluster Local URL: http://myapp.4svg40kna19.svc.cluster.local
@@ -404,14 +404,14 @@ The following example illustrates how to scale your application with the CLI. Yo
404404
405405
5. Run the **`application get`** command again and notice that the value for `Running instances` scaled from zero and information about the instance is displayed.
406406
407-
```sh
407+
```txt
408408
ibmcloud ce application get -n myapp
409409
```
410410
{: pre}
411411
412412
**Example output**
413413
414-
```sh
414+
```txt
415415
Name: myapp
416416
[...]
417417
URL: https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud

Diff for: appdeploy-access.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
copyright:
44
years: 2020, 2022
5-
lastupdated: "2022-01-28"
5+
lastupdated: "2022-02-02"
66

77
keywords: applications in code engine, apps in code engine, http requests in code engine, deploy apps in code engine, app workloads in code engine, deploying workloads in code engine, application, app, memory, cpu, environment variables
88

@@ -44,15 +44,15 @@ To view details of your app with the CLI, use the **`app get`** command. For a c
4444

4545
For example, the following **`app get`** command displays details about the `myapp` app.
4646

47-
```sh
47+
```txt
4848
ibmcloud ce app get --name myapp
4949
```
5050
{: pre}
5151

5252
#### Example output
5353
{: #access-appdetails-cli-example}
5454

55-
```sh
55+
```txt
5656
[...]
5757
OK
5858

0 commit comments

Comments
 (0)