Skip to content

Commit

Permalink
rhdh ado
Browse files Browse the repository at this point in the history
  • Loading branch information
wangzheng422 committed Dec 18, 2024
1 parent cda6b56 commit d5f968f
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 4 deletions.
32 changes: 29 additions & 3 deletions redhat/ocp4/4.16/2024.12.rhdh.ado.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ In this document, we will show you how to integrate `rhdh` with `ado` (azure dev
The architecture is like this:

<!-- ![](./dia/rhdh.ado.drawio.png) -->
<img src="./dia/rhdh.ado.drawio.png" width="400">
<img src="./dia/rhdh.ado.drawio.png" width="800">


> [!NOTE]
Expand Down Expand Up @@ -48,9 +48,9 @@ And set the sso login `demo-backstage` `app registration` permission, based on t
The `app registration` for azure devops integration is `rhdh-azure-devops`, and we keep it as the default settings.

> [!NOTE]
> Recode down the `tenant id`, `client id` and `client secret` for both `app registration`, we will use it in the next step.
> Write down the `tenant id`, `client id` and `client secret` for both `app registration`, we will use it in the next step.
And for demo purpose, we create sever group and users
And for demo purpose, we create several group and users

- L1Support(group)
- l1.u01(user)
Expand Down Expand Up @@ -88,6 +88,12 @@ And in `organization settings`, you can find the `users` settings, add the `app

![](imgs/2024.12.rhdh.ado.md/2024-12-16-22-27-47.png)

Install Code Search Feature for Azure devops

![](imgs/2024.12.rhdh.ado.md/2024-12-18-21-06-38.png)

![](../4.12/imgs/2024-05-16-21-58-16.png)

Now, we finished the azure devops setup, and we can move to the next step.

# rhdh setup
Expand Down Expand Up @@ -322,5 +328,25 @@ you can also see the `repository` is created in the azure devops.

# source code highlight

Here is the example of the `catalog-info.yaml` file, which is created in the azure devops repository. The source code is here, but it is templatized, you can see the result after the creation here, to help you understand the structure.

```yaml
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: dummy-repo-01
title: wzh-demo-component-01
description: wzh-demo-component-01
annotations:
backstage.io/kubernetes-id: dummy-repo-01
backstage.io/techdocs-ref: dir:.
dev.azure.com/project-repo: demo/dummy-repo-01
dev.azure.com/host-org: dev.azure.com/wangzheng422-devops
spec:
type: website
system: wzh-demo
lifecycle: production
owner: user:default/azure.demo.user.01_wzhlab.top
```
# end
2 changes: 1 addition & 1 deletion redhat/ocp4/4.16/2024.12.rhdh.ado.rbac.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ The `app registration` for azure devops integration is `rhdh-azure-devops`, and
> [!NOTE]
> Write down the `tenant id`, `client id` and `client secret` for both `app registration`, we will use it in the next step.
And for demo purpose, we create sever group and users
And for demo purpose, we create several group and users

- L1Support(group)
- l1.u01(user)
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit d5f968f

Please sign in to comment.