domain update

Author: day0hero

content/blog/2022-11-20-argo-rollouts.md

@@ -41,7 +41,7 @@ In this blog, we’re going to use OpenShift Gitops to deploy the Argo Rollouts
 
 ## Preparation
 
-Let’s start by deploying the argo-rollouts pattern from the [argo-rollouts](https://github.com/hybrid-cloud-patterns/argo-rollouts). For this demo, I have deployed a 3-Node compact cluster using `m5.2xlarge` machine types in AWS. This demo will only use rollouts to deploy onto a single cluster.
+Let’s start by deploying the argo-rollouts pattern from the [argo-rollouts](https://github.com/validatedpatterns/argo-rollouts). For this demo, I have deployed a 3-Node compact cluster using `m5.2xlarge` machine types in AWS. This demo will only use rollouts to deploy onto a single cluster.
 
 ```sh
 
@@ -65,15 +65,15 @@ argo-rollouts-7d9dd-master-2   Running   m5.2xlarge   us-east-2   us-east-2c   1
 
 If you've never deployed OpenShift before, you could try [ROSA](https://cloud.redhat.com/learn/getting-started-red-hat-openshift-service-aws-rosa/deploy-rosa-cluster) the pay-as-you-go OpenShift managed service.
 
-Next, you'll need to create a fork of the [argo-rollouts](https://github.com/hybrid-cloud-patterns/argo-rollouts/) repo.
+Next, you'll need to create a fork of the [argo-rollouts](https://github.com/validatedpatterns/argo-rollouts/) repo.
 Go there in a browser, make sure you’re logged in to GitHub, click the “Fork” button, and confirm the destination by clicking the big green "Create fork" button.
 
 Next, [install the Validated Patterns operator](https://validatedpatterns.io/infrastructure/using-validated-pattern-operator/) from Operator Hub.
 
 And finally, click through to the installed operator, and select the `Create
 instance` button and fill out the Create a Pattern form.  Most of the defaults
 are fine, but make sure you update the GitSpec URL to point to your fork of
-`argo-rollouts`, rather than `https://github.com/hybrid-cloud-patterns/argo-rollouts`.
+`argo-rollouts`, rather than `https://github.com/validatedpatterns/argo-rollouts`.
 
 To see what’s going on, click on “Installed Operators” and then change the Project to “All Projects”. After a bit, you will see the following operators installed:
 Advanced Cluster Manager for Kubernetes

content/contribute/extending-a-pattern.adoc

@@ -27,7 +27,7 @@ In the example below AMQ Streams (Kafka) is chosen as a product to add to a patt
 
 == Before starting, fork and clone first
 
-. Visit the github page for the pattern that you wish to extend. E.g. https://github.com/hybrid-cloud-patterns/multicloud-gitops[multicloud-gitops]. Select "`Fork`" in the top right corner.
+. Visit the github page for the pattern that you wish to extend. E.g. https://github.com/validatedpatterns/multicloud-gitops[multicloud-gitops]. Select "`Fork`" in the top right corner.
 . On the create a new fork page. You can choose what owner repository you want and the name of the fork. Most times you will fork into your personal repo and leave the name the same. When you have made the appropriate changes press the "Create fork" button.
 . You will need to clone from the new fork onto you laptop/desktop so that you can do the extension work effectively. So on the new fork's main page elect the green "`Code`" button and copy the git repo's ssh address.
 . In an appropriate directory on your laptop (e.g. `~/git`) use `git clone` on the command line using the ssh address copied above. Then create a branch to extend the pattern. For example if you are extending the `multicloud-gitops` pattern and adding kafka, you will need to clone your fork of multicloud-gitops and create a branch to add Kafka:

content/patterns/devsecops/secure-supply-chain-demo.md

@@ -29,7 +29,7 @@ You will need to login into GitHub and be able to fork two repositories.
 * validatedpatterns/multicluster-devsecops
 
 <!--There is no such repo as chat-client in either orgs -->
-* hybrid-cloud-patterns/chat-client
+* validatedpatterns/chat-client
 
 ## Pipeline Demos
 

content/patterns/medical-diagnosis-amx/ideas-for-customization.adoc

@@ -31,4 +31,4 @@ The {med-pattern} can answer the call to either of these requirements by using
 These are just a few ideas to help you understand how you could use the {med-pattern} as a framework for your application.
 
 //We have relevant links on the patterns page
-//AI: Why does this point to AEG though? https://github.com/hybrid-cloud-patterns/ansible-edge-gitops/issues[Report Bugs]
+//AI: Why does this point to AEG though? https://github.com/validatedpatterns/ansible-edge-gitops/issues[Report Bugs]

modules/basic-secrets-configuration-in-a-clustergroup.adoc

@@ -15,7 +15,7 @@ The pattern framework uses the configured SecretStore backend to inject the secr
 
 The secrets loader in the framework, triggered by `make load-secrets` (also run as part of `make install`), searches for files in the following order and uses the first one found:
 
-* `~/.config/hybrid-cloud-patterns/values-secret-{{ pattern_name }}.yaml`
+* `~/.config/validatedpatterns/values-secret-{{ pattern_name }}.yaml`
 * `~/.config/validated-patterns/values-secret-{{ pattern_name }}.yaml`
 * `~/values-secret-{{ pattern_name }}.yaml`
 * `~/values-secret.yaml`

modules/contributing.adoc

@@ -8,15 +8,15 @@
 
 There are a few different ways you can contribute to Validated Patterns documentation:
 
-* Email the Validated Patterns team at mailto:[email protected][hybrid-cloud-patterns@googlegroups.com].
+* Email the Validated Patterns team at mailto:[email protected][validatedpatterns@googlegroups.com].
 * Create a link:https://github.com/validatedpatterns/docs/issues[GitHub] or link:https://issues.redhat.com/projects/MBP/issues[Jira issue] .
 //to-do: Add link to the contribution workflow when we have a proper one. You might need to create a new file
 * Submit a pull request (PR). To create a PR, create a local clone of your own fork of the link:https://github.com/validatedpatterns/docs[Validated Patterns docs repository], make your changes, and submit a PR. This option is best if you have substantial changes.
 //to-do:For more details on creating a PR see <topic_link_to_contribution_workflow>.
 
 == Contribution workflow
 
-When you submit a PR, the https://github.com/orgs/hybrid-cloud-patterns/teams/docs[Validated Patterns Docs team] reviews the PR and arranges further reviews by Quality Engineering (QE), subject matter experts (SMEs), and others, as required. If the PR requires changes, updates, or corrections, the reviewers add comments in the PR. The documentation team merges the PR after you have implemented all feedback, and you have squashed all commits.
+When you submit a PR, the https://github.com/orgs/validatedpatterns/teams/docs[Validated Patterns Docs team] reviews the PR and arranges further reviews by Quality Engineering (QE), subject matter experts (SMEs), and others, as required. If the PR requires changes, updates, or corrections, the reviewers add comments in the PR. The documentation team merges the PR after you have implemented all feedback, and you have squashed all commits.
 
 
 == Repository organization

static/js/dashboard.js

@@ -166,7 +166,7 @@ function pattern_url(key) {
 }
 
 function repo_url(key) {
-    const prefix = 'https://github.com/hybrid-cloud-patterns/'
+    const prefix = 'https://github.com/validatedpatterns/'
     const dictionary = {
 	aegitops: "ansible-edge-gitops",
 	devsecops: "multicluster-devsecops",