ask before continuing after git update

neu5ron-patch-1
neu5ron 2020-01-03 06:53:51 -05:00
parent 59ba7bf110
commit ebbd962d3d
1 changed files with 8 additions and 7 deletions

View File

@ -421,7 +421,7 @@ UPDATES_FETCHED_FILE="/tmp/helk-update"
REBUILD_NEEDED=0 REBUILD_NEEDED=0
GIT_REPO_CLEAN=1 GIT_REPO_CLEAN=1
echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} You can track the verbose output of this script at $LOGFILE" echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} You can track the verbose output of this script at $LOGFILE\n"
sleep 1 sleep 1
if [[ -e $UPDATES_FETCHED_FILE ]]; then if [[ -e $UPDATES_FETCHED_FILE ]]; then
@ -430,14 +430,15 @@ if [[ -e $UPDATES_FETCHED_FILE ]]; then
if [ "$UPDATES_FETCHED" == "1" ]; then if [ "$UPDATES_FETCHED" == "1" ]; then
echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} Updates for the HELK repository have already been downloaded..." echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} Updates for the HELK repository have already been downloaded..."
# Give user option to clear the feteched updates # Give user option to clear the feteched updates
echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} However, there may be scenarios where you want to re-download and refresh the status of this script..." read -p "Do you to continue without the re-download? (y/n): " -e -i "y" -n 1 -r
read -p "Do you to re-download and refresh the script? (y/n) " -n 1 -r
echo echo
if ! [[ $REPLY =~ ^[Yy]$ ]]; then if [[ $REPLY =~ ^[Yy]$ ]]; then
echo -e "\nExiting script..." update_helk
exit 1 echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} Updates already downloaded. Starting update..."
fi fi
update_helk else
rm $UPDATES_FETCHED_FILE
echo -e "${CYAN}[HELK-UPDATE-INFO]${STD} Re-downloading updates..."
fi fi
fi fi