Fix: permissions for developer tooling config dirs

Since the Dockerfile specifies using UID 1000 instead of root, we now
have to make sure that user can write to the output directories used in
the tooling.

Change-Id: I10f51b44e349abb0b20c4226892880cddd70a9f4

tools/basic-deployment.sh

@@ -13,6 +13,7 @@ BUILD_DIR=$(realpath ${2:-${SCRIPT_DIR}/../build})
 echo === Cleaning up old data ===
 rm -rf ${BUILD_DIR}
 mkdir -p ${BUILD_DIR}
+chmod 777 ${BUILD_DIR}
 
 cp "${CONFIG_SOURCE}"/*.yaml ${BUILD_DIR}
 

tools/g2/stages/build-scripts.sh

@@ -6,6 +6,7 @@ source "${GATE_UTILS}"
 
 cd "${TEMP_DIR}"
 mkdir scripts
+chmod 777 scripts
 
 log Building scripts
 docker run --rm -t \

tools/g2/stages/generate-certificates.sh

@@ -6,6 +6,7 @@ source "${GATE_UTILS}"
 
 OUTPUT_DIR="${TEMP_DIR}/config"
 mkdir -p "${OUTPUT_DIR}"
+chmod 777 "${OUTPUT_DIR}"
 
 for source_dir in $(config_configuration); do
     log Copying configuration from "${source_dir}"

tools/gate/build.sh

@@ -24,6 +24,10 @@ echo Usinag image ${IMAGE_PROMENADE}.
 echo === Cleaning up old data ===
 rm -f config/*
 rm -f promenade-bundle/*
+mkdir -p config
+chmod 777 config
+mkdir -p promenade-bundle
+chmod 777 promenade-bundle
 
 echo === Validating test environment ===
 env -i - $(cat default-config-env) env $(cat $ENV_PATH) $GATE_DIR/util/validate-test-env.sh