Skip to content
This repository was archived by the owner on Nov 5, 2024. It is now read-only.

Commit 8080467

Browse files
authored
Merge pull request #122 from jc-berger/registry-based-images-in-builds
added section for registry base images
2 parents 386b34d + 8043c7a commit 8080467

File tree

2 files changed

+40
-2
lines changed

2 files changed

+40
-2
lines changed

docs/modules/.DS_Store

0 Bytes
Binary file not shown.

docs/modules/ROOT/pages/how-to-guides/Import-code/proc_importing_code.adoc

Lines changed: 40 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,45 @@ For more information about devfile contents requirements, see the "What is outer
214214
+
215215
**Solution:** Select a predefined runtime type from the **Review and configure for deployment** view. Make sure you meet all of the {ProductName} <<repository requirements>> for the runtime you select, or configure your own <<custom build and deployment instructions>>.
216216

217+
=== Creating a Red Hat Container Registry token
218+
219+
After importing your code, configure a Red Hat Container Registry token to improve your application-building experience. You can access this token by creating Red Hat registry service accounts. The registry service accounts enable you to retrieve content from *registry.redhat.io*. *Registry.redhat.io* helps you manage the automation of your applications.
220+
221+
.Procedure
222+
223+
Create the Red Hat Container Registry token by following these steps:
224+
225+
. Go to link:https://access.redhat.com/terms-based-registry/#/[registry service accounts].
226+
. Create a registry service account by clicking *New Service Account*.
227+
. Fill in the *Name* and *Description* field.
228+
. Click *Create*.
229+
. For *Token Information*, click *Docker Configuration*.
230+
. Enter the following Dockerfile registry authentication code:
231+
```
232+
{
233+
"auths": {
234+
"registry.redhat.io": {
235+
"auth": "MTEwNzAxOTl8-redacted-c2Jvc2U6ZZlNDQ="
236+
}
237+
}
238+
}
239+
```
240+
241+
=== Configuring your application to use a Red Hat Container Registry token
242+
243+
After creating the Red Hat Container Registry token, include the token in your application. When your application includes the Red Hat Container Registry token, you can access *registry.redhat.io* which improves your automation.
244+
245+
.Procedure
246+
247+
. Go to *Component Settings*.
248+
. Select *Create new build secret*.
249+
. In the *Create new build secret* modal, add the *registry.redhat.io* token that you want to use as a pull secret:
250+
.. In the *Key* field, enter *.dockerconfigjson*.
251+
.. In the *Select or Enter Name* field, enter *registry-redhat.io*.
252+
.. Enter the registry service account token and click *Create*.
253+
.. From your command line, run the `oc secrets link appstudio-pipeline registry-redhat-io` command.
254+
217255
[role="_additional-resources"]
218256
.Additional resources
219-
For information about importing and configuring code to {ProductName} using the CLI, see link:https://redhat-appstudio.github.io/docs.stonesoup.io/Documentation/main/getting-started/getting_started_in_cli/#getting-started-in-the-cli[Getting started in the CLI
220-
].
257+
258+
For information about importing and configuring code to {ProductName} using the CLI, see link:https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/getting-started/getting_started_in_cli/#getting-started-in-the-cli[Getting started in the CLI].

0 commit comments

Comments
 (0)