From 180e543e6648c602bc877bd84c1d62f0fa589430 Mon Sep 17 00:00:00 2001 From: Elsa Mayra Irgens Date: Fri, 20 Dec 2024 12:51:46 +0100 Subject: [PATCH] Removed refs to (now) deleted repos --- public-site/docs/guides/git-submodules/index.md | 6 +----- public-site/docs/guides/volume-mounts/index.md | 4 ++-- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/public-site/docs/guides/git-submodules/index.md b/public-site/docs/guides/git-submodules/index.md index 053ea1a4..5330aaba 100644 --- a/public-site/docs/guides/git-submodules/index.md +++ b/public-site/docs/guides/git-submodules/index.md @@ -14,14 +14,10 @@ As of December 2022, Radix only supports a single SSH key for authenticating to There is an option to update submodule within the pipeline job. Please look [at the example](/guides/git-submodules/update-submodule-in-pipeline-job.md). ::: -## Sample application with git submodule - -[This GitHub repository](https://github.com/equinor/radix-app-with-submodule-example) contains a Radix application that has a single component, `redis`. This component is built from the source code inside the `redis` directory, and this directory is in turn a git submodule which points to a git repository at https://github.com/equinor/radix-submodule-example. Take note that the remote URL of the submodule is HTTPS and not SSH; unauthenticated clone via SSH, even for public repositories, is not supported. - ### Trigger build of main app with commit to submodule By default, a submodule reference is statically locked to a single commit in the remote repository. E.g. a dynamic reference to a branch of the submodule is not possible. If a new commit is made in the sub-module, this will not be reflected in the main repository unless the main repository is updated with a new commit reference. -A development team might want a change in the submodule to be automatically reflected in parent repositories. This can be achieved with a GitHub actions workflow on the submodule repository which automatically updates the parent repositories. The submodule in the example has [such a workflow](https://github.com/equinor/radix-submodule-example/blob/main/.github/workflows/push-to-main-repo.yml). +A development team might want a change in the submodule to be automatically reflected in parent repositories. This can be achieved with a GitHub actions workflow on the submodule repository which automatically updates the parent repositories. The example workflow uses a deploy key with write access to automatically modify the parent repository when the submodule is modified. If a new commit is made to the `main` branch of the submodule, the `main` branch of the parent repository gets a new commit which changes the submodule reference to point to HEAD of the submodule's `main` branch. diff --git a/public-site/docs/guides/volume-mounts/index.md b/public-site/docs/guides/volume-mounts/index.md index cba19781..cc56f9e6 100644 --- a/public-site/docs/guides/volume-mounts/index.md +++ b/public-site/docs/guides/volume-mounts/index.md @@ -64,7 +64,7 @@ volumes: and files appear inside the container. If there are folders within blob container - it will exist in the pod's container as well ```sh -kubectl exec -it -n radix-csi-azure-example-dev deploy/frontend -- ls -l /app/image-storage +kubectl exec -it -n radix-example-dev deploy/frontend -- ls -l /app/image-storage total 0 -rwxrwxrwx 1 root root 21133 Nov 13 13:56 image-01.png -rwxrwxrwx 1 root root 21989 Nov 13 13:56 image-02.png @@ -136,7 +136,7 @@ volumes: and files appear inside the container ```sh -kubectl exec -it -n radix-csi-azure-example-dev deploy/frontend -- ls -lR /app +kubectl exec -it -n radix-example-dev deploy/frontend -- ls -lR /app /app: total 4 drwxrwxrwx 2 root root 4096 Dec 11 15:10 image-storage