[arvados] updated: 2.6.0-305-g81e02a8fc

[git repository hosting]

Summary of changes:
 doc/install/salt-multi-host.html.textile.liquid  | 2 +-
 doc/install/salt-single-host.html.textile.liquid | 2 +-
 tools/salt-install/installer.sh                  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

       via  81e02a8fc1aa079e1cb9448a23beba631b6fa807 (commit)
      from  73a972b5affef724905e4ce4c4c916c48d145b34 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 81e02a8fc1aa079e1cb9448a23beba631b6fa807
Author: Lucas Di Pentima <lucas.dipentima at curii.com>
Date:   Tue Jun 27 10:29:27 2023 -0300

    20665: Fixes logic script error & minor docs improvements.
    
    Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <lucas.dipentima at curii.com>

diff --git a/doc/install/salt-multi-host.html.textile.liquid b/doc/install/salt-multi-host.html.textile.liquid
index 7403dacc2..27e732164 100644
--- a/doc/install/salt-multi-host.html.textile.liquid
+++ b/doc/install/salt-multi-host.html.textile.liquid
@@ -263,7 +263,7 @@ h2(#localparams). Edit @local.params*@ files
 
 The cluster configuration parameters are included in two files: @local.params@ and @local.params.secrets at . These files can be found wherever you choose to initialize the installation files (e.g., @~/setup-arvados-xarv1@ in these examples).
 
-The @local.params.secrets@ file is intended to store security-sensitive data such as passwords, private keys, tokens, etc. Depending on the security requirements of the cluster deployment, you may wish to store this file in a secrets store like AWS secrets manager or Jenkins credentials.
+The @local.params.secrets@ file is intended to store security-sensitive data such as passwords, private keys, tokens, etc. Depending on the security requirements of the cluster deployment, you may wish to store this file in a secrets store like AWS Secrets Manager or Jenkins credentials.
 
 h3. Parameters from @local.params@:
 
diff --git a/doc/install/salt-single-host.html.textile.liquid b/doc/install/salt-single-host.html.textile.liquid
index 82a1137bc..8ad79d86e 100644
--- a/doc/install/salt-single-host.html.textile.liquid
+++ b/doc/install/salt-single-host.html.textile.liquid
@@ -108,7 +108,7 @@ h2(#localparams). Edit @local.params*@ files
 
 The cluster configuration parameters are included in two files: @local.params@ and @local.params.secrets at . These files can be found wherever you choose to initialize the installation files (e.g., @~/setup-arvados-xarv1@ in these examples).
 
-The @local.params.secrets@ file is intended to store security-sensitive data such as passwords, private keys, tokens, etc. Depending on the security requirements of the cluster deployment, you may wish to store this file in a secrets store like AWS secrets manager or Jenkins credentials.
+The @local.params.secrets@ file is intended to store security-sensitive data such as passwords, private keys, tokens, etc. Depending on the security requirements of the cluster deployment, you may wish to store this file in a secrets store like AWS Secrets Manager or Jenkins credentials.
 
 h3. Parameters from @local.params@:
 
diff --git a/tools/salt-install/installer.sh b/tools/salt-install/installer.sh
index b042d1a83..4ce490421 100755
--- a/tools/salt-install/installer.sh
+++ b/tools/salt-install/installer.sh
@@ -127,7 +127,7 @@ deploynode() {
 }
 
 loadconfig() {
-    if [[ -s ${CONFIG_FILE} && -s ${CONFIG_FILE}.secrets ]]; then
+    if ! [[ -s ${CONFIG_FILE} && -s ${CONFIG_FILE}.secrets ]]; then
 		echo "Must be run from initialized setup dir, maybe you need to 'initialize' first?"
     fi
     source ${CONFIG_FILE}.secrets

-----------------------------------------------------------------------


hooks/post-receive
--