Skip to content

Commit 16dc096

Browse files
committed
update
1 parent 36af90b commit 16dc096

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

content/modules/ROOT/pages/02-introduction.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Red Hat Trusted Application Pipeline and Red Hat OpenShift AI
44

55
This demonstration takes the audience on a journey across the Software Development Lifecycle (SDLC), from code, to build, through continuous deployment and finally to running in production. An end-to-end DevSecOps CI/CD demonstration of Red Hat Trusted Application Pipeline (RHTAP) incorporating Developer Hub, a developer self-service portal based on Backstage, to standardize and expedite developer onboarding with golden path templates imbued with security guardrails.
66

7-
In addition to the SDLC is also the MDLC (Model Development Lifecycle) where LLMs are served/managed by Red Hat OpenShift AI. These LLMs are then woven into an application. Offering self-service capabilities for Coders and Modelers.
7+
In addition to the SDLC is also the MDLC (Model Development Lifecycle) where LLMs are served/managed by Red Hat OpenShift AI. These LLMs are then woven into an application. Offering self-service capabilities for Coders and Modelers.
88

99
Featured products in this demonstration include:
1010

@@ -28,9 +28,9 @@ This is the story of how Red Hat imbues your software supply chain with the cont
2828

2929
You might have heard the phrase "shift-left" as it relates to security practices. That phrase primarily focuses on the idea that security checks should not simply be executed manually (human-powered) and at the very end of the path-to-production pipeline but brought forward in time.
3030

31-
In this demonstration, we are going to see the ultimate of "shift-left" by introducing security checks at the point of code entry. We are also going to see "shift-down", injection of security practices from the moment of project creation, embodied by the golden path template, and fully integrated into the platform itself.
31+
In this demonstration, we are going to see the ultimate of "shift-left" by introducing security checks at the point of code entry. We are also going to see "shift-down", injection of security practices from the moment of project creation, embodied by the golden path template, and fully integrated into the platform itself.
3232

33-
Remember the ultimate goal of a well managed platform-as-a-product (PaaP) is to serve its customers, and in the case of an IDP, that means the enterprise application development teams. The IDP can best serve its customers by dramatically lowering the developer's cognitive load, allowing app devs to focus on the code that contributes to the next business outcome.
33+
Remember the ultimate goal of a well managed platform-as-a-product (PaaP) is to serve its customers, and in the case of an IDP, that means the enterprise application development teams. The IDP can best serve its customers by dramatically lowering the developer's cognitive load, allowing app devs to focus on the code that contributes to the next business outcome.
3434

3535
In this story, we are are going to hear about 3 major new ideas:
3636

@@ -40,7 +40,7 @@ In this story, we are are going to hear about 3 major new ideas:
4040
4141
No tickets, no wait, let's go
4242

43-
Please contact the RHTAP product team on https://redhat.enterprise.slack.com/archives/C06D1L9N6J3 [Slack] for assistance and to provide feedback related to these materials. (Note: Please open the link in a new tab)
43+
Please contact the RHTAP product team on https://redhat.enterprise.slack.com/archives/C06D1L9N6J3 [Slack] for assistance and to provide feedback related to these materials. (Note: Please open the link in a new tab)
4444

4545
== Demo Startup
4646

@@ -50,15 +50,15 @@ Please give this demo a further 10 to 15 minutes to start up completely once the
5050

5151
Consider the following steps *BEFORE* sharing your screen with the audience. This allows the presenter to switch between the developer and platform engineer (PE) perspectives. During the majority of the presentation you are primarily within the developer perspective, focusing on Developer Hub as the primary user experience.
5252

53-
* Browser 1: login as developer
53+
* Browser 1: login as developer
5454
* Browser 2: login as platform engineer - using incognito mode or a 2nd browser (e.g. Firefox vs Safari)
5555
* Run the end-to-end to cache images and validate your flow/narrative
5656
* Previously tested a Dev Space or
5757
* Double check your local laptop git, mvn and IDE (VS Code, IntelliJ) are ready to go
5858

5959
A super short video on the https://www.youtube.com/watch?v=n1IrNe5MmZg[core value propositions] of *Backstage*.
6060

61-
== Login as developer
61+
== Login as developer
6262

6363
image::login-dev-user1-1.png[]
6464

@@ -74,7 +74,7 @@ Click *Authorize*
7474

7575
image::login-dev-user1-4.png[]
7676

77-
Enter an email address for Keycloak like `user1@opentlc.com`
77+
Enter an email address for Keycloak like `user1@demo.redhat.com`
7878

7979
image::login-dev-user1-5.png[]
8080

@@ -159,7 +159,7 @@ click *IMPORT*
159159

160160
image::setup-templates-3.png[]
161161

162-
Then click on *Create...* in the left-hand navigation menu and you will see several more templates related to things like Python, Node.js, Spring Boot, C# etc.
162+
Then click on *Create...* in the left-hand navigation menu and you will see several more templates related to things like Python, Node.js, Spring Boot, C# etc.
163163

164164
image::setup-templates-4.png[]
165165

content/modules/ROOT/pages/10-signed-commits.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ Run the following commands to set up gitsign on your local machine. For this ex
138138

139139
[source,console]
140140
----
141-
$ git config --global user.email user1@opentlc.com
141+
$ git config --global user.email user1@demo.redhat.com
142142
$ git config --global user.name user1
143143
$ git config --global commit.gpgsign true
144144
$ git config --global tag.gpgsign true

0 commit comments

Comments
 (0)