Updating all casl-ansible references to openshift-applier

README.md

@@ -18,7 +18,7 @@ We understand that everyone's definition of a pipeline is a little (maybe a lot)
 In this context, a _pipeline_ is defined as all of the technical collateral required to take application source code and get it deployed through it's relevant lifecycle environments on an OpenShift cluster (or multiple clusters).
 
 A few guiding principles for a pipeline quickstart in this repo:
-- **Everything as code**. A pipeline should require as few commands as possible to deploy (We reccommend an [openshift-applier](https://github.com/redhat-cop/casl-ansible/tree/master/roles/openshift-applier) compatible inventory)
+- **Everything as code**. A pipeline should require as few commands as possible to deploy (We recommend an [openshift-applier](https://github.com/redhat-cop/openshift-applier) compatible inventory)
 - **Use OpenShift Features**. The intention of these quickstarts is to showcase how OpenShift can be used to make pipeline development and management simpler. Use of features like slave pods, webhooks, source to image and the `JenkinsPipelineStrategy` is highly desired where possible.
 - **Sharing is Caring**. If there are things that can be common to multiple pipelines (templates, builder images, etc.), let's refactor to make them shared.
 
@@ -43,4 +43,4 @@ See our [basic spring boot](./basic-spring-boot) example for a very simple refer
 
 ## Automated Deployments
 
-These pipeline quickstarts include an Ansible inventory through which they can be automatically deployed and managed using the [OpenShift Applier](https://github.com/redhat-cop/casl-ansible/tree/master/roles/openshift-applier) role.
+These pipeline quickstarts include an Ansible inventory through which they can be automatically deployed and managed using the [OpenShift Applier](https://github.com/redhat-cop/openshift-applier) role.

basic-spring-boot/README.md

@@ -7,7 +7,7 @@ This example demonstrates how to implement a full end-to-end Jenkins Pipeline fo
 * "One Click" instantiation of a Jenkins Pipeline using OpenShift's Jenkins Pipeline Strategy feature
 * Promotion of an application's container image within an OpenShift Cluster (using `oc tag`)
 * Promotion of an application's container image to a separate OpenShift Cluster (using `skopeo`) - Coming Soon!
-* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/casl-ansible/tree/master/roles/openshift-applier) Ansible role.
+* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/openshift-applier.git) project.
 
 ## Automated Quickstart
 

basic-tomcat/README.md

@@ -7,21 +7,21 @@ This example demonstrates how to implement a full end-to-end Jenkins Pipeline fo
 * "One Click" instantiation of a Jenkins Pipeline using OpenShift's Jenkins Pipeline Strategy feature
 * Promotion of an application's container image within an OpenShift Cluster (using `oc tag`)
 * Promotion of an application's container image to a separate OpenShift Cluster (using `skopeo`)
-* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/casl-ansible/tree/master/roles/openshift-applier) Ansible role.
+* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/openshift-applier.git) project.
 
 ## Quickstart
 
 ### Requirements
-1. [OpenShift Applier](https://github.com/redhat-cop/casl-ansible)
-   `git clone git@github.com:redhat-cop/casl-ansible.git`
+1. [OpenShift Applier](https://github.com/redhat-cop/openshift-applier)
+   `git clone git@github.com:redhat-cop/openshift-applier.git`
    `git checkout v3.6.1`
 2. [Ansible](https://www.ansible.com/)
    `sudo dnf install ansible`
 
 ### Installation
 Run the following commands to instantiate this example.
 ```
-ansible-playbook -i inventory/hosts ../casl-ansible/playbooks/openshift-cluster-seed.yml --connection=local
+ansible-playbook -i inventory/hosts ../openshift-applier/playbooks/openshift-cluster-seed.yml --connection=local
 ```
 The above command will create all the necessary projects and OpenShift objects as well as a Jenkins instance that will build, promote and deploy the application.
 Run the following commands to instantiate this example.

multi-cluster-spring-boot/README.md

@@ -7,7 +7,7 @@ This example demonstrates how to implement a full end-to-end Jenkins Pipeline fo
 * "One Click" instantiation of a Jenkins Pipeline using OpenShift's Jenkins Pipeline Strategy feature
 * Promotion of an application's container image within an OpenShift Cluster (using `oc tag`)
 * Promotion of an application's container image to a separate OpenShift Cluster (using `skopeo`)
-* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/casl-ansible/tree/master/roles/openshift-applier) Ansible role.
+* Automated rollout using the [openshift-appler](https://github.com/redhat-cop/openshift-applier.git) project.
 
 ## Prerequisites
 
@@ -23,12 +23,12 @@ This quickstart can be deployed quickly using Ansible. Here are the steps.
 
 1. Clone [this repo](https://github.com/redhat-cop/container-pipelines.git)
 2. `cd container-pipelines/multi-cluster-spring-boot`
-3. Run `ansible-galaxy install -r requirements.yml --roles-path=roles`
+3. Run `ansible-galaxy install -r requirements.yml --roles-path=galaxy`
 4. Log into your _Prod_ OpenShift cluster, and run the following command.
     ```
     $ oc login <prod cluster>
     ...
-    $ ansible-playbook -i ./applier/inventory-prod/ roles/casl-ansible/playbooks/openshift-cluster-seed.yml
+    $ ansible-playbook -i ./applier/inventory-prod/ galaxy/openshift-applier/playbooks/openshift-cluster-seed.yml
     ```
 5. One of the things that was created by ansible is a `ServiceAccount` that will be used for promoting your app from _Dev_ to _Prod_. We'll need to extract its credentials so that our pipeline can use that account.
     ```
@@ -45,7 +45,7 @@ This quickstart can be deployed quickly using Ansible. Here are the steps.
     ```
     $ oc login <dev cluster>
     ...
-    $ ansible-playbook -i ./applier/inventory-dev/ /path/to/casl-ansible/playbooks/openshift-cluster-seed.yml
+    $ ansible-playbook -i ./applier/inventory-dev/ galaxy/openshift-applier/playbooks/openshift-cluster-seed.yml
     ```
 
 At this point you should have 3 projects deployed (`multicluster-spring-boot-dev`, `multicluster-spring-boot-stage`, and `multicluster-spring-boot-prod`) with our [Spring Rest](https://github.com/redhat-cop/spring-rest.git) demo application deployed to all 3.

multi-cluster-spring-boot/requirements.yml

@@ -1,8 +1,8 @@
 # This is the Ansible Galaxy requirements file to pull in the correct roles
 # to support the operation of CASL provisioning/runs.
 
-# From 'casl-ansible'
-- name: casl-ansible
+# From 'openshift-applier'
+- name: openshift-applier
   scm: git
-  src: https://github.com/redhat-cop/casl-ansible
-  version: v3.7.1
+  src: https://github.com/redhat-cop/openshift-applier
+  version: v3.9.0