Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added docs for dev spaces #242

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

added docs for dev spaces #242

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions content/patterns/devsecops/devspaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: OpenShift DevSpaces
weight: 50
aliases: /devsecops/devspaces/
---

# DevSpaces

## Introduction

This pattern also includes [OpenShift DevSpaces](https://access.redhat.com/products/red-hat-openshift-dev-spaces) as a way to model the inner loop for developers.

In order to allow developers to push code changes back to the SCM, it's necessary to configure a secret.

You should put the secret in the `~/values-secret-multicluster-devsecops.yaml` file (or the file you are using for secrets). The secret you add should look like this:

```yaml
- name: github-devspaces
fields:
- name: client-secret
value: xxx
- name: client-id
value: yyy
```

The name of the secret and of the fields cannot be changed. The values must be generated following the approach described [here](https://www.eclipse.org/che/docs/stable/administration-guide/configuring-oauth-2-for-github/#setting-up-the-github-oauth-app). Just obtain the secret values. Do not manually create the secret in the cluster and described in the following section of the docs.

At the moment only github is tested.