Merge branch 'update-repo-url' into 'master'

update umbrella repo url\references

See merge request platform-one/big-bang/bigbang!238

charter/VendorDistroIntegration.md

@@ -20,6 +20,6 @@ A working example for rke2 can be found [here][2] (Note this link is pinned to a
 
 You can find more information about specific jobs in each jobs specific README.md inside [umbrella-templates][1]
 
-[0]: https://repo1.dso.mil/platform-one/big-bang/umbrella/-/pipelines
+[0]: https://repo1.dso.mil/platform-one/big-bang/bigbang/-/pipelines
 [1]: https://repo1.dso.mil/platform-one/big-bang/pipeline-templates/umbrella-templates
-[2]: https://repo1.dso.mil/platform-one/big-bang/umbrella/-/blob/a1b7926ce05127a57661fe5ff72c6d7a23db0470/.gitlab-ci.yml#L148
+[2]: https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/a1b7926ce05127a57661fe5ff72c6d7a23db0470/.gitlab-ci.yml#L148

docs/4_configuration.md

@@ -124,7 +124,7 @@ In your `kustomization.yaml` under your environment, here is an example of how t
 
 ```yaml
 bases:
-- https://repo1.dso.mil/platform-one/big-bang/umbrella.git/base/?ref=v1.2.*
+- https://repo1.dso.mil/platform-one/big-bang/bigbang.git/base/?ref=v1.2.*
 patchesStrategicMerge:
 - |-
   apiVersion: source.toolkit.fluxcd.io/v1beta1

docs/5_deployment.md

@@ -116,7 +116,7 @@ The following commands will help you monitor the progress of the Big Bang deploy
 
    # 'bigbang' READY should be True
     NAME            URL                                                        READY   STATUS                                                                      AGE
-    bigbang         https://repo1.dso.mil/platform-one/big-bang/umbrella.git   True    Fetched revision: master/8a4a1ddd0c9edf316f5362680cf2921baf0c3451   25m
+    bigbang         https://repo1.dso.mil/platform-one/big-bang/bigbang.git   True    Fetched revision: master/8a4a1ddd0c9edf316f5362680cf2921baf0c3451   25m
    ```
 
 1. Verify the Big Bang Helm Chart was deployed
@@ -137,7 +137,7 @@ The following commands will help you monitor the progress of the Big Bang deploy
    # The Git repository holding the Helm charts for each package can be seen in the URL column.
    # The STATUS column shows the branch and tag of the revision being used.
     NAMESPACE     NAME              URL                                                                             READY   STATUS                                                                      AGE
-    bigbang       bigbang           https://repo1.dso.mil/platform-one/big-bang/umbrella.git                        True    Fetched revision: master/3a44686520152e576a8c2c6f264876efff497c4b           8m25s
+    bigbang       bigbang           https://repo1.dso.mil/platform-one/big-bang/bigbang.git                        True    Fetched revision: master/3a44686520152e576a8c2c6f264876efff497c4b           8m25s
     bigbang       logging           https://repo1.dso.mil/platform-one/big-bang/apps/core/logging.git               True    Fetched revision: release-v0.2.x/9cfe1e14c12098464ee89eb877614f781cd78fb7   8m23s
     bigbang       certmanager       https://repo1.dso.mil/platform-one/big-bang/apps/sandbox/cert-manager.git       True    Fetched revision: release-v1.0.x/1247135baf145dcfad4a4a02ef679c48fb76d9fb   8m23s
     bigbang       istio             https://repo1.dso.mil/platform-one/big-bang/apps/core/servicemesh.git           True    Fetched revision: chart-release/2b02a51b7950ce21bac26403fa25d09e7e3f86c3    8m23s

docs/c_development.md

@@ -8,11 +8,11 @@ Included here is a setup that will allow you to checkout and begin development u
 
 #### Access
 + [AWS GovCloud (US) EC2](https://console.amazonaws-us-gov.com/ec2)
-+ [Umbrella repository](https://repo1.dso.mil/platform-one/big-bang/umbrella)
++ [Umbrella repository](https://repo1.dso.mil/platform-one/big-bang/bigbang)
 + [Iron Bank registry](https://registry1.dso.mil/)
 
 - [AWS GovCloud (US) EC2](https://console.amazonaws-us-gov.com/ec2)
-- [Umbrella repository](https://repo1.dsop.io/platform-one/big-bang/umbrella)
+- [Umbrella repository](https://repo1.dsop.io/platform-one/big-bang/bigbang)
 - [Iron Bank registry](https://registry1.dsop.io/)
 
 #### Utilities
@@ -274,8 +274,8 @@ kubectl get nodes
 
 mkdir -pv ~/repos/
 cd ~/repos
-git clone https://repo1.dso.mil/platform-one/big-bang/umbrella.git
-cd ~/repos/umbrella
+git clone https://repo1.dso.mil/platform-one/big-bang/bigbang.git
+cd ~/repos/bigbang
 ```
 
 From the base of the project

package.json

@@ -3,7 +3,7 @@
   "description": "Big Bang is a declarative, continuous delivery tool for core DoD hardened and approved [packages](#packages) into a Kubernetes cluster.  Big Bang follows a [GitOps](#gitops) approach to configuration management, using [Flux v2](#flux-v2) to reconcile Git with the cluster.  Environments (e.g. dev, prod) and packages (e.g. istio) can be fully configured to suit the deployment needs.",
   "repository": {
     "type": "git",
-    "url": "https://repo1.dso.mil/platform-one/big-bang/umbrella.git"
+    "url": "https://repo1.dso.mil/platform-one/big-bang/bigbang.git"
   },
   "devDependencies": {
     "@commitlint/cli": "^11.0.0",

tests/ci/shared-secrets.yaml

@@ -20,7 +20,7 @@ spec:
   interval: 1m0s
   # NOTE: We could use the same "bigbang" repository, but secrets are usually committed to a consumer owned repo,
   #       so we are demonstrating that here with a new `GitRepository` resource pointed to the same repo
-  url: https://repo1.dso.mil/platform-one/big-bang/umbrella.git
+  url: https://repo1.dso.mil/platform-one/big-bang/bigbang.git
   ref:
     branch: master
 ---