Merge pull request #5 from 1Password/connor/update-docker-hub

Changed docker image reference to new hub organization

docker-compose/README.md

@@ -27,6 +27,6 @@ Once your scimsession file has been created, copy it into this directory (next t
 
 Next, edit `docker-compose.yml`, replacing `{YOUR-DOMAIN-HERE}` with the domain name indicated by the DNS record created for your SCIM bridge. This will configure LetsEncrypt to automatically issue a certificate for your bridge.
 
-Running `docker-compose up --build` will now create a container from the `onepassword/scim` image. A redis container will also be started automatically to be used by the SCIM bridge. _After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine.
+Running `docker-compose up --build` will now create a container from the `1password/scim` image. A redis container will also be started automatically to be used by the SCIM bridge. _After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine.
 
 Once you have tested the configuration, the bridge can be exited using ctrl/cmd-c, and restarted in daemon mode using `docker-compose up -d, or deployed for production use with Docker Swarm or Kubernetes. You can access logs using `docker-compose logs` at any point in the future.

docker-compose/docker-compose.yml

@@ -2,7 +2,7 @@ version: '3.3'
 
 services:
     scim:
-        image: onepassword/scim:v0.4.4
+        image: 1password/scim:v0.5
         ports: 
             - "80:8080"
             - "443:8443"

docker-swarm/README.md

@@ -25,4 +25,4 @@ Once your scimsession file has been created, copy it into this directory (next t
 
 Next, edit `docker-compose.yml`, replacing `{YOUR-DOMAIN-HERE}` with the domain name indicated by the DNS record created for your SCIM bridge. This will configure LetsEncrypt to automatically issue a certificate for your bridge.
 
-Running `docker stack deploy -c docker-compose.yml op-scim` will now create a container from the `onepassword/scim` image. A redis container will also be started automatically to be used by the SCIM bridge. _After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine using `docker service logs -f op-scim_scim`.
+Running `docker stack deploy -c docker-compose.yml op-scim` will now create a container from the `1password/scim` image. A redis container will also be started automatically to be used by the SCIM bridge. _After the DNS record has been propogated_, you can continue setting up your IdP with the SCIM bridge Administration Guide while monitoring the logs from the bridge on your local machine using `docker service logs -f op-scim_scim`.

docker-swarm/docker-compose.yml

@@ -2,7 +2,7 @@ version: '3.3'
 
 services:
     scim:
-        image: onepassword/scim:v0.4.4
+        image: 1password/scim:v0.5
         deploy:
           replicas: 1
           restart_policy:

kubernetes/op-scim-deployment.yaml

@@ -14,7 +14,7 @@ spec:
     spec:
       containers:
       - name: op-scim
-        image: onepassword/scim:v0.4.4
+        image: 1password/scim:v0.5
         command: ["./op-scim"]
         args: ["--session=/secret/scimsession", "--letsencrypt-domain={YOUR-DOMAIN-HERE}"]
         ports:

session/create-session-file.sh

@@ -2,7 +2,7 @@
 
 mkdir session
 
-docker run -it -v $PWD/session:'/op-scim/session' onepassword/scim /op-scim/create-session-docker.sh
+docker run -it -v $PWD/session:'/op-scim/session' 1password/scim /op-scim/create-session-docker.sh
 
 cp ./session/scimsession ./scimsession
 rm -rf ./session