Skip to content

devspaces.md

Latest commit

 

History

History
28 lines (20 loc) · 1.08 KB

devspaces.md

File metadata and controls

28 lines (20 loc) · 1.08 KB
title OpenShift DevSpaces
weight 50
aliases /devsecops/devspaces/

DevSpaces

Introduction

This pattern also includes OpenShift DevSpaces 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:

   - 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. 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.