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

Next publish push

Author: foverby

Diff for: appdeploy-update.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-13"
+lastupdated: "2022-01-27"
 
 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
 
@@ -527,7 +527,7 @@ From the previous example, the `myhelloapp` app references the `us.icr.io/myname
 
 1.  Create the build configuration. For example, the following **`build create`** command creates a build configuration that is called `helloworld-build`. This configuration builds from the public Git repo `https://github.com/IBM/CodeEngine`, uses the `dockerfile` strategy and `medium` build size, and stores the image to `us.icr.io/mynamespace/codeengine-helloworld` by using the image registry secret that is defined in `myregistry`.
 
-    ```sh
+    ```txt
     ibmcloud ce build create --name helloworld-build --image us.icr.io/mynamespace/codeengine-helloworld --registry-secret myregistry --source https://github.com/IBM/CodeEngine --commit main --context-dir /hello --strategy dockerfile --size medium
     ```
     {: pre}

Diff for: build.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2022
-lastupdated: "2022-01-20"
+lastupdated: "2022-01-27"
 
 keywords: builds for code engine, builds, building, source code, build run, application image builds for code engine, job image builds for code engine, container image builds with code engine
 
@@ -62,7 +62,7 @@ For example, the following **`build create`** command creates a build configurat
 If you are using the `--strategy` option with the value of `dockerfile`, then ensure the `--dockerfile` option is correctly set to the name of the `dockerfile`. The default value for the `--strategy` option is `Dockerfile`. 
 {: important}
 
-```sh
+```txt
 ibmcloud ce build create --name helloworld-build --image us.icr.io/mynamespace/codeengine-helloworld --registry-secret myregistry --source https://github.com/IBM/CodeEngine --commit main --context-dir /hello --strategy dockerfile --size medium
 ```
 {: pre}
@@ -191,7 +191,7 @@ ibmcloud ce build create --name helloworld-build-private --image us.icr.io/mynam
 
 You can create a build configuration that pulls source from a local directory by using only the {{site.data.keyword.codeengineshort}} CLI. You must specify the details of your source repository, the build [strategy](/docs/codeengine?topic=codeengine-plan-build#build-strategy), and the [build size](/docs/codeengine?topic=codeengine-plan-build#build-size) that you decided to use, and the container image details to store the container image.
 
-When you submit a build that pulls code from a local directory, your source code is packed into an archive file and uploaded to your {{site.data.keyword.registrylong_notm}} instance. You can choose to ignore certain file patterns from within your source code by using the `.ceignore` file, which behaves similarly to a `.gitignore` file. The source image is created in the same namespace as your build image.
+When you submit a build that pulls code from a local directory, your source code is packed into an archive file and uploaded to your {{site.data.keyword.registrylong_notm}} instance. Note that you can only target {{site.data.keyword.registrylong_notm}} for your local builds. You can choose to ignore certain file patterns from within your source code by using the `.ceignore` file, which behaves similarly to a `.gitignore` file. The source image is created in the same namespace as your build image.
 
 Creating a build configuration does not create an image, but creates the configuration to build an image. You must then run a build that references the build configuration to create an image. The build configuration is not validated or used to create an image until the build is run. The build configuration enables multiple subsequent builds of an image, such as when changes are applied to the source repository.
 {: tip}
@@ -208,10 +208,10 @@ Before you begin
 - [Create and work with a project](/docs/codeengine?topic=codeengine-manage-project).
 - [Create a registry secret so you can save your image](/docs/codeengine?topic=codeengine-add-registry).
 
-The following example command creates a build configuration that pulls source from a local directory, puts the image in the `mynamespace` namespace that is defined in `us.icr.io`, and uses the `myregistry` registry access secret that is known to {{site.data.keyword.codeengineshort}}.
+The following example command creates a build configuration that pulls source from a local directory, puts the image in the `mynamespace` namespace that is defined in `us.icr.io`, and uses the `myregistry` registry access secret that is known to {{site.data.keyword.codeengineshort}}. When you specify `local` as the value for `-build-type`, you can only target {{site.data.keyword.registrylong_notm}} for the output of your local build. 
 
 ```sh
-ibmcloud ce build create -name build-local-dockerfile -build-type local -image us.icr.io/mynamespace/codeengine-build --registry-secret myregistry  -dockerfile Dockerfile -strategy dockerfile -size medium
+ibmcloud ce build create --name build-local-dockerfile --build-type local --image us.icr.io/mynamespace/codeengine-build --registry-secret myregistry --dockerfile Dockerfile --strategy dockerfile --size medium
 ```
 {: pre}
 
@@ -320,8 +320,8 @@ The following scenario clones the [Samples for {{site.data.keyword.codeengineful
 
 3. From the directory where your source code resides, submit the build run. The following example runs a build that is called `buildrun-local-dockerfile`and uses the `build-local-dockerfile` build configuration. The `--source` option specifies the path to the source on the local machine to the `helloworld` sample.
 
-    ```sh
-    ibmcloud ce buildrun submit buildrun submit -n buildrun-local-dockerfile -b build-local-dockerfile -source ./helloworld  
+    ```txt
+    ibmcloud ce buildrun submit --name buildrun-local-dockerfile --build build-local-dockerfile --source ./helloworld  
     ```
     {: pre}
 

Diff for: cli-changelog.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-20"
+lastupdated: "2022-01-27"
 
 keywords: cli change log for code engine, cli version for code engine, change log for cli in code engine, cli history for code engine, change log, cli version history
 
@@ -20,6 +20,7 @@ Find a summary of changes for each version of {{site.data.keyword.codeenginefull
 
 | Version | Release date | Changes |
 | ----- | ------- | -------------- |
+| 1.25.2 | 27 January 2022| - Fixed various bugs. |
 | 1.25.0 | 20 January 2022| - Added support for creating a build that pulls source from a local directory. Added the `--build-type` option to the **`build create`** command, with values of `git` or `local`. The default for this option is `git`. Added the `--source` option to the **`buildrun submit`** command which is valid when the `build-type` is `local`. \n - Fixed various bugs. |
 | 1.24.0 | 13 January 2022| - Added the **`application restart`** and **`jobrun restart`** commands to restart running app and job run instances. \n - Added the **`buildrun cancel`** command to stop a running build run.  \n -  Added support for working with configuration maps and secrets with jobs and job runs as mounted files. For this support, added the `--mount-configmap` and `--mount-secret` options to the **`job create`**, **`job update`**, **`jobrun submit`** and **`jobrun resubmit`** commands. Added the `--mount-rm` option to the **`job update`** and **`jobrun resubmit`** commands to remove the contents of the configmap or secret from the file system for the job or job run. Updated the output for the **`job get`** and **`jobrun get`** commands to add a `Mounts` section to display information about mounted files.  \n - Updated description of `kubecfg` option for the **`project select`** command to clarify that the `KUBECONFIG` environment variable can be used to override the Kubernetes configuration file. \n - Fixed various bugs. \n - Updated translations for the CLI. \n - Upgraded to Go 1.17.6.|
 | 1.23.3 | 15 December 2021 | - Fixed various bugs.  \n - Updated translations for the CLI. \n - Upgraded to Go 1.17.5. |