Bump versions of meta-sota utilities

Change-Id: I36a4d3d24826ab8776bc980b50aef8606af9e7a8
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>

1 files changed, 7 insertions, 9 deletions

diff --git a/README.md b/README.md
index 0e47cf6..4ea5da5 100644
--- a/README.md
+++ b/README.md
@@ -49,11 +49,9 @@ SOTA-related variables in local.conf
 * OSTREE_INITRAMFS_IMAGE - initramfs/initrd image that is used as a proxy while
   booting into OSTree deployment. Do not change this setting unless you are
   sure that your initramfs can serve as such proxy.
-* OSTREE_REMOTE_URL - when set adds pushing your ostree commit to a remote
-  repo. Defaults to an empty string.
-* OSTREE_REMOTE_USER and OSTREE_REMOTE_PASSWORD - should be set if
-  OSTREE_REMOTE_URL is set. Used to authenticate to the server set in
-  OSTREE_REMOTE_URL. Both default to an empty string.
+* OSTREE_PUSH_CREDENTIALS - when set adds pushing your ostree commit to a remote
+  repo. sota-tools will then use credentials in the file pointed to by this
+  variable.
 
 Usage
 -----
@@ -100,8 +98,8 @@ changes in OSTree repository generated by bitbake process. It communicates with
 an http server capable of querying files with HEAD requests and uploading them
 with POST requests. garage-push is used as following:
 
-    garage-push --repo=/path/to/ostree-repo --ref=mybranch --url=https://my.ostree.server/ --user=username --password=password
+    garage-push --repo=/path/to/ostree-repo --ref=mybranch --credentials=~/.sota-tools.json --user=username --password=
 
-You can set OSTREE_REMOTE_URL, OSTREE_REMOTE_USER and OSTREE_REMOTE_PASSWORD in
-your local.conf to make your build results be automatically synchronized with a
-remote server.
+You can set OSTREE_PUSH_CREDENTIALS in your local.conf to make your build
+results be automatically synchronized with a remote server.
+Credentials are stored in JSON format which is described in [sota-tools documentation](https://github.com/advancedtelematic/sota-tools/blob/master/README.adoc)