From 2c3339eae9ff44ce92043a08cecacfb937b3b10e Mon Sep 17 00:00:00 2001 From: Raffaele Spazzoli Date: Thu, 2 Mar 2023 11:43:10 -0500 Subject: [PATCH] added docs for dev spaces --- content/patterns/devsecops/devspaces.md | 28 +++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 content/patterns/devsecops/devspaces.md diff --git a/content/patterns/devsecops/devspaces.md b/content/patterns/devsecops/devspaces.md new file mode 100644 index 000000000..996106474 --- /dev/null +++ b/content/patterns/devsecops/devspaces.md @@ -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. \ No newline at end of file