Merge pull request #176 from cloud-docs/next-prod-push

Next publish push

Author: Kersten Richter

about.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2021
-lastupdated: "2021-12-15"
+lastupdated: "2021-12-21"
 
 keywords: benefits, terminology, developers, capabilities, code engine
 

app-tutorial.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2021
-lastupdated: "2021-12-15"
+lastupdated: "2021-12-21"
 
 keywords: app tutorial for code engine, application, apps, images, tutorial for code engine, deploying
 
@@ -15,7 +15,7 @@ completion-time: 10m
 
 {{site.data.keyword.attribute-definition-list}}
 
-# Deploying applications
+# Deploying and scaling applications
 {: #deploy-app-tutorial}
 {: toc-content-type="tutorial"}
 {: toc-completion-time="10m"}

appdeploy-plan.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2021
-lastupdated: "2021-11-16"
+lastupdated: "2021-12-20"
 
 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
 
@@ -18,7 +18,7 @@ subcollection: codeengine
 An application, or app, runs your code to serve HTTP requests. In addition to traditional HTTP requests, {{site.data.keyword.codeenginefull}} also supports applications that use WebSockets as their communications protocol. The number of running instances of an app are automatically scaled up or down (to zero) based on incoming workloads and your configuration settings. An app contains one or more revisions. A revision represents an immutable version of the configuration properties of the app. Each update of an app configuration property creates a new revision of the app. 
 {: shortdesc}
 
-**Before you begin**
+Before you begin
 
 * If you want to use the {{site.data.keyword.codeengineshort}} console, go to [{{site.data.keyword.codeengineshort}} overview](https://cloud.ibm.com/codeengine/overview){: external}. 
 * If you want to use the CLI, [set up your {{site.data.keyword.codeengineshort}} CLI environment](/docs/codeengine?topic=codeengine-install-cli).
@@ -29,7 +29,7 @@ An application, or app, runs your code to serve HTTP requests. In addition to tr
 ## Plan a container image for {{site.data.keyword.codeengineshort}} applications
 {: #deploy-app-containerimage}
 
-To deploy applications in {{site.data.keyword.codeengineshort}}, you need to first create a container image that has all of the runtime artifacts your application needs to run, such as runtime libraries. You can use many different methods to create the image, including building your app from source code by using the [build container images](/docs/codeengine?topic=codeengine-build-image) feature available in {{site.data.keyword.codeengineshort}}. Your image can be downloaded from either a public or private image registry. For more information, see [Accessing container registries](/docs/codeengine?topic=codeengine-add-registry).
+To deploy applications in {{site.data.keyword.codeengineshort}}, you need to first create a container image that includes the runtime artifacts that your application needs to run, such as runtime libraries. You can use many different methods to create the image, including building your app from source code by using the [build container images](/docs/codeengine?topic=codeengine-build-image) feature available in {{site.data.keyword.codeengineshort}}. Your image can be downloaded from either a public or private image registry. For more information, see [Accessing container registries](/docs/codeengine?topic=codeengine-add-registry).
 
 When you deploy your application, the most current version of your referenced container image is downloaded and deployed.
 

appdeploy-public.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2021
-lastupdated: "2021-11-15"
+lastupdated: "2021-12-15"
 
 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
 
@@ -71,31 +71,9 @@ https://myapp.4idmmq6xpss.us-south.codeengine.appdomain.cloud
 
 The following table summarizes the options that are used with the **`app create`** command in this example. For more information about the command and its options, see the [**`ibmcloud ce app create`**](/docs/codeengine?topic=codeengine-cli#cli-application-create) command.
 
-<table>
-<caption><code>application create</code> command components</caption>
-<thead>
-<col width="25%">
-<col width="75%">
-<th colspan=2><img src="images/idea.png" alt="Idea icon"/> Understanding this command's components</th>
-</thead>
-<tbody>
-<tr>
-<td><code>--name</code></td>
-<td>The name of the application. Use a name that is unique within the project. This value is required.
-<ul>
-<li>The name must begin with a lowercase letter.</li>
-<li>The name must end with a lowercase alphanumeric character.</li>
-<li>The name must be 55 characters or fewer and can contain letters, numbers, and hyphens (-).</li>
-</ul>
-</td>
-</tr>
-<tr>
-<td><code>--image</code></td>
-<td>The name of the image that is used for this application. This value is required. The format is <code>REGISTRY/NAMESPACE/REPOSITORY:TAG</code> where <code>REGISTRY</code> and <code>TAG</code> are optional. If <code>TAG</code> is not specified, the default is <code>latest</code>. For images in <a href="https://hub.docker.com/">Docker Hub</a>, you can specify the image with <code>NAMESPACE/REPOSITORY</code>, as the default for <code>Registry</code> is <code>docker.io</code>. For other registries, use <code>REGISTRY/NAMESPACE/REPOSITORY</code> or <code>REGISTRY/NAMESPACE/REPOSITORY:TAG</code>. 
-</td>
-</tr>
-</tbody>
-</table>
-
-
-
+| Option | Description |
+| -------------- | -------------- |
+| `--name` | The name of the application. Use a name that is unique within the project. This value is required. \n - The name must begin with a lowercase letter. \n - The name must end with a lowercase alphanumeric character. \n - The name must be 55 characters or fewer and can contain letters, numbers, and hyphens (-). | 
+| `--image` | The name of the image that is used for this application. This value is required. The format is `REGISTRY/NAMESPACE/REPOSITORY:TAG` where `REGISTRY` and `TAG` are optional. If `TAG` is not specified, the default is `latest`. For images in [Docker Hub](https://hub.docker.com/){: external}, you can specify the image with `NAMESPACE/REPOSITORY`, as the default for `Registry` is `docker.io`. For other registries, use `REGISTRY/NAMESPACE/REPOSITORY` or `REGISTRY/NAMESPACE/REPOSITORY:TAG`. |
+{: caption="Table 1. Command description" caption-side="bottom"}
+ 

appdeploy-update.md

@@ -86,7 +86,7 @@ To update your app with the CLI, use the **`app update`** command. This command
 
 Update the application that you created in [Deploying an application with the CLI](/docs/codeengine?topic=codeengine-deploy-app#deploy-app-cli) to add an environment variable. 
 
-The sample `docker.io/ibmcom/hello ` image reads the environment variable `TARGET`, and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. The following example updates the app to modify the value of the `TARGET` environment variable to `Stranger`.
+The sample `docker.io/ibmcom/hello` image reads the environment variable `TARGET`, and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. The following example updates the app to modify the value of the `TARGET` environment variable to `Stranger`.
 
 1. Run the **`application update`** command. For example,
 

at-events.md

@@ -1,7 +1,7 @@
 ---
 copyright:
   years: 2020, 2021
-lastupdated: "2021-10-06"
+lastupdated: "2021-12-15"
 
 keywords: events, serverless, code engine, activity tracker, analyzing events
 
@@ -237,24 +237,18 @@ Note:
 After you view events that are captured by {{site.data.keyword.at_full_notm}}, you can then analyze the events.
 {: shortdesc}
 
-**Identifying the {{site.data.keyword.codeengineshort}} project that generates the event**.
+Identifying the {{site.data.keyword.codeengineshort}} project that generates the event
+:    To identify the project for which the event was generated, look at the `target.id` field. You can use this field to filter events in {{site.data.keyword.loganalysisshort_notm}}, for example, showing events for only a specific project. 
+:    You can use the CLI to find details about your [project](/docs/codeengine?topic=codeengine-manage-project).
 
-To identify the project for which the event was generated, look at the `target.id` field. You can use this field to filter events in {{site.data.keyword.loganalysisshort_notm}}, for example, showing events for only a specific project. 
+Getting the unique ID of a request
+:    Each action that you perform on a {{site.data.keyword.codeengineshort}} project resource has a unique ID.
+:    To find the unique ID of a request, look at the `correlationId` value that is set in the `correlationId` field.
 
-You can use the CLI to find details about your [project](/docs/codeengine?topic=codeengine-manage-project).
+Getting information for failures
+:    All events that are issued for failed actions display `failure` in the `outcome` field, and in addition provide more details as part of the `reason` field. Note that the `reason.reasonForFailure` field might be especially helpful, as it contains details of the failure. 
 
-**Getting the unique ID of a request**
-
-Each action that you perform on a {{site.data.keyword.codeengineshort}} project resource has a unique ID.
-
-To find the unique ID of a request, look at the `correlationId` value that is set in the `correlationId` field.
-
-**Getting information for failures**
-
-All events that are issued for failed actions display `failure` in the `outcome` field, and in addition provide more details as part of the `reason` field. Note that the `reason.reasonForFailure` field might be especially helpful, as it contains details of the failure. 
-
-**Custom views**
-
-For more information about generating custom views by using event fields, see [Creating custom views in {{site.data.keyword.loganalysislong_notm}}](/docs/activity-tracker?topic=activity-tracker-views).
+Custom views
+:    For more information about generating custom views by using event fields, see [Creating custom views in {{site.data.keyword.loganalysislong_notm}}](/docs/activity-tracker?topic=activity-tracker-views).
 
 

batch-tutorial.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2021
-lastupdated: "2021-11-17"
+lastupdated: "2021-12-21"
 
 keywords: job tutorial, jobs, images for code engine jobs, tutorial for code engine, job log
 
@@ -15,7 +15,7 @@ completion-time: 10m
 
 {{site.data.keyword.attribute-definition-list}}
 
-# Running jobs
+# Running and updating jobs 
 {: #run-job-tutorial}
 {: toc-content-type="tutorial"}
 {: toc-completion-time="10m"}
@@ -25,7 +25,7 @@ With this tutorial, run a batch job by using the {{site.data.keyword.codeenginef
 
 A job runs one or more instances of your executable code. Unlike applications, which handle HTTP requests, jobs are designed to run one time and exit. When you create a job, you can specify workload configuration information that is used each time that the job is run.
 
-**Before you begin**
+Before you begin
 
 To use the {{site.data.keyword.codeengineshort}} console, go to [{{site.data.keyword.codeengineshort}} overview](https://cloud.ibm.com/codeengine/overview){: external}. 
 
@@ -58,7 +58,7 @@ After you create your job and specify your workload configuration information, y
     * From the Jobs page, click the name of the job that you want to run. 
 
 2. From your job page, in the Jobs pane, click **Submit job**. 
-3. From the Submit job pane, accept all of the default values, and click **Submit job** again to run your job.
+3. From the Submit job pane, accept all the default values, and click **Submit job** again to run your job.
 
 From the Submit job pane, you can review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. You can specify either **Number of instances** or **Array indices** for the number of parallel job instances to run. For **Number of instances**, provide the number of instances to run in parallel for this job. For **Array indices**, provide a comma-separated list for your custom set of indices. For example, to run this job with a custom set of `5` indices, specify `3,12-14,25`. After you submit this job, the system displays the status of the instances of your job on the Job details page. If you specify **Number of instances** instead of **Array indices** in the Submit job pane, from the `Configuration` section of the Job details page, this information is provided as **Array indices**.
 {: note} 

build-tutorial-buildpacks.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2021
-lastupdated: "2021-11-17"
+lastupdated: "2021-12-20"
 
 keywords: code engine, tutorial, build, source, application, buildpack, access, build run, image
 
@@ -20,7 +20,6 @@ completion-time: 10m
 {: toc-content-type="tutorial"}
 {: toc-completion-time="10m"}
 
-With this tutorial, build a container image from source with the {{site.data.keyword.codeengineshort}} CLI. The build process uses the [buildpacks strategy](/docs/codeengine?topic=codeengine-plan-build#build-strategy) and stores the image from the build process on Docker Hub.
 {: shortdesc}
 
 A build, or image build, is a mechanism that you can use to create a container image from your source code. {{site.data.keyword.codeengineshort}} supports building from a Dockerfile and Cloud Native Buildpacks.
@@ -78,7 +77,7 @@ OK
 ```
 {: screen}
 
-The `size` option specifies the size for the build, which determines the amount of resources that are used. Valid values are `small`, `medium`, `large`, `xlarge`. The `size` reflects the build requirements for your source code for your app or job. If the build fails due to lack of memory or disk space, or is not fast enough, try switching to a larger size. A larger build size also means that more memory and CPU cores are assigned to the build process. Increasing this size will probably speed up the build process, but this action also increases the cost. For more information about builds, check the [troubleshooting tips](/docs/codeengine?topic=codeengine-troubleshoot-build).
+The `size` option specifies the size for the build, which determines the amount of resources that are used. Valid values are `small`, `medium`, `large`, `xlarge`. The `size` reflects the build requirements for your source code for your app or job. If the build fails due to lack of memory or disk space, or is not fast enough, try switching to a larger size. A larger build size also means that more memory and CPU cores are assigned to the build process. Increasing this size can probably speed up the build process, but this action also increases the cost. For more information about builds, check the [troubleshooting tips](/docs/codeengine?topic=codeengine-troubleshoot-build).
 {: tip}
 
 ## Submit a build run