Build 2025

Author: cfsdocs

add-registry.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-11"
+lastupdated: "2024-01-19"
 
 keywords: registries, container registry, image registry, apikey, API key, access token, images, registry access, registry secret, service id,registry secret, registry access secret
 
@@ -186,20 +186,31 @@ To set up access to an {{site.data.keyword.registryfull_notm}} in a different {{
 
 To add {{site.data.keyword.registryfull_notm}} or Docker Hub access with the console,
 
-1. Go to the [{{site.data.keyword.codeengineshort}} dashboard](https://cloud.ibm.com/codeengine/overview).
-2. Select a project (or [create one](/docs/codeengine?topic=codeengine-manage-project#create-a-project)).
-3. From the project page, click **Registry access**.
-4. Click **Create**.
-5. Select **Docker Hub** or **Custom**.
-6. Enter a name for your registry access.
-7. Enter a server name for your registry. For {{site.data.keyword.registryshort}}, the server name is `<region>.icr.io`. For example, `us.icr.io`. For [Docker Hub](https://hub.docker.com/), the server name is `https://index.docker.io/v1/`.
-8. Enter a username. For {{site.data.keyword.registryfull_notm}}, it is `iamapikey`. For Docker Hub, it is your Docker ID.
-9. Enter the password. For {{site.data.keyword.registryfull_notm}}, the password is your API key. For Docker Hub, you can use your Docker Hub password or an [access token](#access-private-docker-hub).
-10. Click **Create**.
-
-You can add access to a container registry when you create an application or job, or when you build an image. Click **Configure image** and specify the container image to run, including the registry where the image is stored and the [registry access](/docs/codeengine?topic=codeengine-add-registry#types-registryaccesssecrets) to use to retrieve the image.  Follow previous steps 5-9.
+
+
+**REVIEW**
+
+Before you begin, [create a project](/docs/codeengine?topic=codeengine-manage-project).
+
+1. After your project is in **Active** status, click the name of your project on the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}. 
+2. From the Components page, click **Secrets and configmaps**.
+3. From the Secrets and configmaps page, click **Create** to create your secret.
+4. From the Create secret or configmap page, complete the following steps:
+    1. Select **Registry secret**, and click **Next**.
+    2. Provide a name; for example, `mysecret-registry`.
+    3. Specify the target registry for this secret, such as {{site.data.keyword.registrylong_notm}} or Docker Hub.
+    4. Specify the location of the registry. 
+    5. Specify a username. If this secret is for {{site.data.keyword.registrylong_notm}}, the username is `iamapikey`. If this secret is for Docker Hub, it is your Docker ID.
+    6. Enter the credentials for the username. For {{site.data.keyword.registryfull_notm}}, use your IAM API key. For Docker Hub, you can use your Docker Hub password or an [access token](#access-private-docker-hub). For other target registries, specify the password or API key for the username.
+    7. Click **Create** to create the secret. 
+
+Now that your secret is created from the console, go to the Secrets and configmaps page to view a list of defined secrets and configmaps. You can apply filters to customize the list to meet your needs. 
+
+You can add access to a container registry when you create an application or job, or when you build an image. Click **Configure image** and specify the container image to run, including the registry where the image is stored and the [registry access](/docs/codeengine?topic=codeengine-add-registry#types-registryaccesssecrets) to use to retrieve the image. 
 {: tip}
 
+**/REVIEW**
+
 ### Adding registry access with the CLI
 {: #add-registry-access-ce-cli}
 

build-private.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-11"
+lastupdated: "2024-01-19"
 
 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, registry secret, registry access secret
 
@@ -31,7 +31,7 @@ You can choose to ignore certain file patterns from within your source code by u
 3. From the project page, click **Image builds**.
 4. From the **Image build** tab, click **Create**. The **Specify build details** side panel opens where you enter the details of your build.
 5. In the **Source** section, enter a name for your build, the URL of your source repository, and your code repo access. 
-    - If your code is in a private repo, use an SSH URL for the code repository URL and either select the name of an existing code repo access or [create a code repo access](/docs/codeengine?topic=codeengine-code-repositories). An example of an SSH URL is `[email protected]:IBM/CodeEngine.git`. 
+    - If your code is in a private repo, use an SSH URL for the code repository URL and either select the name of an existing SSH secret or [create an SSH secret](/docs/codeengine?topic=codeengine-code-repositories). An example of an SSH URL is `[email protected]:IBM/CodeEngine.git`. 
     - Optionally, select a source branch name. If you do not provide a branch name and you leave the field empty, {{site.data.keyword.codeengineshort}} automatically uses the default branch of the specified repository. You can enter any other branch name, tag, or commit ID.
 
     Click **Next** to continue. 

configmap.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2020, 2023
-lastupdated: "2023-12-19"
+  years: 2020, 2024
+lastupdated: "2024-01-19"
 
 keywords: configmaps with code engine, key references with code engine, key-value pair with code engine, setting up configmaps with code engine, configmaps, environment variables
 
@@ -53,12 +53,13 @@ Before you begin, [create a project](/docs/codeengine?topic=codeengine-manage-pr
 1. After your project is in **Active** status, click the name of your project on the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}. 
 2. From the Overview page, click **Secrets and configmaps**.
 3. From the Secrets and configmaps page, click **Create** to create your configmap.  
-4. From the Create config page, complete the following steps.
-    1. Select the **Configmap** option.  
+4. From the Create secret or configmap page, complete the following steps:
+    1. Click **Configmap**, and click **Next**. 
     2. Provide a name; for example, `myconfigmap`.
     3. Click **Add key-value pair**. Specify one or more key-value pairs for this configmap. For example, specify one key as `key1` with the value of `value1` and specify another key as `key2` with the value of `value2`. Notice that you can specify values on one or more lines. The name that you choose for your key does not need to be the same as the name of your environment variable.
     4. Click **Create** to create the configmap. 
-5. Now that your configmap is created from the console, go to the Secrets and configmaps page to view a listing of defined secrets and configmaps.
+
+Now that your configmap is created from the console, go to the Secrets and configmaps page to view a list of defined secrets and configmaps. You can apply filters to customize the list to meet your needs.
 
 ### Create a configmap with the CLI
 {: #configmap-create-cli}

landing.json

@@ -1,6 +1,6 @@
 {
     "title": "Code Engine",
-    "lastupdated": "2024-01-17",
+    "lastupdated": "2024-01-19",
     "introduction": "Find out how you can use Code Engine to run your containerized workloads",
     "section_devtools": {
       "api": "/apidocs/codeengine/v2", 

plan-repo.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2024
-lastupdated: "2024-01-12"
+lastupdated: "2024-01-19"
 
 keywords: repository access for code engine, source code access for code engine, access to source code in code engine, access keys in code engine, ssh key access in code engine, github repo access in code engine, gitlab repo access in code engine, code repository access for code engine, code repositories, Git repository access secret, code repository, private git repository, private repository, SSH secret
 
@@ -23,7 +23,7 @@ After you create access to your private code repository, you can pull code from
 ## Create code repository access
 {: #create-code-repo}
 
-When you create access to a private code repository, you are saving credentials in {{site.data.keyword.codeengineshort}}. In the console, these credentials are called *Code repo access*. In the CLI, these credentials are called *SSH secrets*.
+When you create access to a private code repository, you are saving credentials in {{site.data.keyword.codeengineshort}}. These credentials are called *SSH secrets*.
 
 Before you begin
 
@@ -54,13 +54,18 @@ Do not create your SSH key file with a secure passphrase as this action causes y
 ### Adding private repository access from the console
 {: #add-repo-access-ce-console}
 
-To add private repository access from the console,
+Before you begin, [create a project](/docs/codeengine?topic=codeengine-manage-project).
 
-1. Go to the [{{site.data.keyword.codeengineshort}} dashboard](https://cloud.ibm.com/codeengine/overview).
-2. Select a project (or [create one](/docs/codeengine?topic=codeengine-manage-project#create-a-project)).
-3. From the project page, click **Code repo access**.
-4. Click **Create**.
-5. Specify a name, Code repo server, and the [SSH key](#choose-ssh-key).
+1. After your project is in **Active** status, click the name of your project on the [{{site.data.keyword.codeengineshort}} Projects page](https://cloud.ibm.com/codeengine/projects){: external}. 
+2. From the Components page, click **Secrets and configmaps**.
+3. From the Secrets and configmaps page, click **Create** to create your secret.
+4. From the Create secret or configmap page, complete the following steps:
+    1. Select **SSH secret**, and click **Next**.
+    2. Provide a name; for example, `mysecret-ssh`.
+    3. Add the SSH private key for this secret. 
+    4. Click **Create** to create the secret. 
+
+Now that your secret is created from the console, go to the Secrets and configmaps page to view a list of defined secrets and configmaps. You can apply filters to customize the list to meet your needs. 
 
 You can create access when you build an image.
 {: tip}

release-notes.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-17"
+lastupdated: "2024-01-19"
 
 keywords: release notes for code engine, updates in code engine, what's new in code engine, document changes in code engine, updates, release notes
 
@@ -30,11 +30,11 @@ Review the release notes for January 2024.
 {: #codeengine-janxx24}
 {: release-note}
 
-**REVIEW**
-
-[Update]{: tag-magenta} Updated the user experience for making configuration changes to apps and jobs in the console.
-:   {{site.data.keyword.codeengineshort}} has enhanced the user experience to simplify deploying configuration changes for applications and jobs. When you work in the {{site.data.keyword.codeengineshort}} console, instead of specifically entering an edit mode before you can make configuration changes, you can make changes to your configuration settings and deploy to make your changes effective. You can also redeploy your application without changes to configuration settings, if needed. See [update your application](/docs/codeengine?topic=codeengine-update-app).
+[Update]{: tag-magenta} Updated the user experience for making configuration changes to apps in the console.
+:   {{site.data.keyword.codeengineshort}} has enhanced the user experience to simplify deploying configuration changes for applications. When you work in the {{site.data.keyword.codeengineshort}} console, instead of specifically entering an edit mode before you can make configuration changes, you can make changes to your configuration settings and deploy to make your changes effective. You can also redeploy your application without changes to configuration settings, if needed. See [Update your application](/docs/codeengine?topic=codeengine-update-app).
 
+[Update]{: tag-magenta} Updated the user experience for creating secrets and configmaps in the console.
+:   {{site.data.keyword.codeengineshort}} has enhanced the user experience to simplify creating and working with secrets and configmaps in the console. See [Working with secrets](/docs/codeengine?topic=codeengine-secret) and [Working with configmaps](/docs/codeengine?topic=codeengine-configmap).
 
 
 ### 12 January 2024