Merge ~elmo/charm-memcached:juju-config-not-set into charm-memcached:master

[James Troup]

Replace references to 'juju set' with 'juju config'

[🤖 prod-jenkaas-bootstack (prod-jenkaas-bootstack)]

A CI job is currently in progress. A follow up comment will be added when it completes.

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

This merge proposal is being monitored by mergebot. Change the status to Approved to merge.

[🤖 prod-jenkaas-bootstack (prod-jenkaas-bootstack)]

PASSED: Continuous integration, rev:291c846d8eecb394f2692bbcb21b9de313ce13f5
https://jenkins.canonical.com/bootstack/job/lp-charm-memcached-ci/1/
Executed test runs:
    SUCCESS: https://jenkins.canonical.com/bootstack/job/lp-charm-test-unit/154/
    None: https://jenkins.canonical.com/bootstack/job/lp-update-mp/392/

Click here to trigger a rebuild:
https://jenkins.canonical.com/bootstack/job/lp-charm-memcached-ci/1//rebuild

review: Approve (continuous-integration)

[Celia Wang (ziyiwang)]

lgtm

review: Approve

[🤖 Canonical IS Merge Bot (canonical-is-mergebot)]

Change successfully merged at revision 9b9ee3629e349e5ac1309214a660040228d6780c

diff --git a/README.md b/README.md
index c6b831a..be2385b 100644
--- a/README.md
+++ b/README.md
@@ -34,12 +34,12 @@ Then deploy a maximum of 2 units of memcached:
     juju deploy -n 2 config.yaml memcached
 
 **Caution** : As per design limitations, If you try to add another unit of memcached, all the units will be 
-set as standalone you decide to disable repcached by using `juju set memcached repcached=false` and re-deploy the
+set as standalone you decide to disable repcached by using `juju config memcached repcached=false` and re-deploy the
 unit.
 
 Or you can deploy 2 units and then enable replication by running
     juju deploy -n 2 memcached
-    juju set memcached repcached=true
+    juju config memcached repcached=true
 
 
 ### Removing a unit
@@ -47,7 +47,7 @@ Or you can deploy 2 units and then enable replication by running
 Removing one of the cluster units, means remove replication, please disable replication first
 and then remove the unit safely.
 
-    juju set memcached repcached=false
+    juju config memcached repcached=false
     juju remove-unit memcached/0
 
 
@@ -55,7 +55,7 @@ and then remove the unit safely.
 
 For turning the replication support off on memcached, you need to run the following command:
 
-    juju set memcached repcached=false
+    juju config memcached repcached=false
 
 ## Example Usage
 
diff --git a/hooks/memcached_hooks.py b/hooks/memcached_hooks.py
index 796e8c4..657cdc3 100755
--- a/hooks/memcached_hooks.py
+++ b/hooks/memcached_hooks.py
@@ -156,7 +156,7 @@ def cluster_relation_changed():
             else:
                 msg = """This unit will be marked as failed because
                 Repcached replication only can take place between two units.
-                If you want to disable this set 'juju set repcached=false'"""
+                If you want to disable this set 'juju config repcached=false'"""
                 log(msg, level="WARN")
                 raise Exception(msg)
         except AttributeError:
diff --git a/hooks/replication.py b/hooks/replication.py
index 426d8cc..9c56a23 100644
--- a/hooks/replication.py
+++ b/hooks/replication.py
@@ -41,7 +41,7 @@ def get_current_replica():
             msg = """Cannot configure replication between more than 2 units,
             all the units are going to be setup as standalone. Please
             remove the remaining units with 'juju remove-unit', and
-            then set 'juju set memcached repcached=true' again"""
+            then set 'juju config memcached repcached=true' again"""
             log(msg, level="WARN")
         else:
             try: