heavy_script

[Bugfix]

• use posix compliant test for shell evaluation (#46)
• • Fixes errors in command to container when testing which shell is available
• • Contributor: @justsomescripts

[Breaking Changes]

• These are optional, which is why I didn't push a major change
• • Add script to global with the menu, option 5, then option 3
• • Even if you ran this previously, you should do it again, as the method has changed (yeah.. its only been a day, my bad.)
• • This will run the one line download, so then HeavyScript can be invoked with a terminal emulator with just 'heavyscript'
    NOTE: This does NOT work with CronJobs, you will still need the full path to the file etc.

[Features]

• One line install
• This will:
• • Download the script and place it in /root
• • Allow users to run the script from any directory with a terminal emulator
• • Places users on the latest tag/release automatically

[Features]

• Add ability to add script to Global Path, allowing users to access the script from any directory with just heavy_script.sh

• • Activate this from the menu, option 5, then option 3.
    NOTE: This currently does not work for cron jobs. I will add that in a later patch, so keep your full paths in your cron jobs for now

• Added Colors to Errors, Warning, Successes, as well as important data.

• • It's hard to cover all bases, so If you come across something weird, or something that should be colored, open an issue.
    NOTE: No colors will ever be added for things that can be run as a cron job, since it mangles output for the email

[Features]

• Mounting/Unmounting PVC's
• • Gives users the ability to mount to whatever pool they want
• • Added colors for warnings, errors, and successful mounts
• • Completely redid the output for mounting, seriously check it out.

[Refactor]

• Process applications that should or should not go to post processing prior to sending them there
• Indentation after some IF statements etc.

• Bugfix
• • Fix tail'ing lines in container logs

• Added

• • Ability to choose a branch or tag from the menu, so you can checkout beta features, if any are available
• • New backup/restore window
• • HeavyScript title colors
• • View container Logs

• Bug Fixes

• • Fixed while loop in backup asking if you'd like to continue deleting backups.
• • Use local patch rather than pulling from Truetool repo

• Other

• • General Refactor, added comments, broke stuff up into functions, easier to read code etc..

Hotpatch 2

• Fixes the issue where some applications will stop the backup process, creating a dead restore point.
  -- How to use
  --- bash heavy_script.sh option 9

Note: This was a patch file created from a commit upstream, this was never a heavyscript issue to begin with.

• Remove function export error
• Add Shellcheck linter to Github Actions
• Note:
• • See previous release notes if you are running Bluefin(22.12.0) and have not yet ran the restore/backup patch

• Backups (#33)
• • Ix-systems broke backups for PVC data
• • Any backups taken while on bluefin PRIOR to running the patch will result in a FAILURE
• • To fix this, there is an included patch, here are the steps to run it:

1. run bash heavyscript.sh
2. choose option 8

If you need help with this contact me on discord "Heavybullets#5535" or open a github issue

• Backups (#34)
• • Commit warning if user is attempting to restore a backup from an earlier release
• • Exit the restore process if user is attempting to restore to a backup with missing PVC data for applications that are SUPPOSED to have PVC data
• • • This is to prevent further damage and storage loss for those applications. Since rolling back to a restore point like this would fail anyway.

Prune

• Use CLI prune if version is Bluefin or greater (#30 #31)
• • Truenas SCALE Bluefin has been released

• Mounting

• • Fixed issue with similar names being recognized in the status pull, ensuring applications that may already be stopped, are not then "stopped" again

• Restoring

• • Restrict ZFS list to the releases folder, ensuring backups of ix-application are not pulled

• Restoring
• • Set ZFS properties for application volumes, prior to restoring
• • • Ensures off-site backups are restored with the correct ZFS properties

• Mounting
• • Use ZFS list -r to restrict to the current app pool only
• • Systems with more than one pool will see a speed improvement

• Include TrueTool in delete overflow and listing backups (#29)
• • Allows for seamless migration from TrueTool users.
• Use $app rather than index counter (#29)

• Improve Commander Function (#26)

• • Remove un-needed variables and checks

• Sort by ix-names for command to container, increasing accuracy (#26)

• Improve speed by not sending the exceptions below to pre-processing (#27)

• • Ignore / Prev Failed / Major Versions / Container Images

• Add option to ignore container image updates with --ignore-img (#28)

• Compact Backup options to unclutter menu (#21)
• Do not send container image updates for post processing (#22)
• Do not Update applications if they are stuck deploying (#23)
• Cleanup Commander Function (#24)

• Improve DNS Function (#19) (#20)

• • No longer need a long ignore list
• • List more readable name next to DNS name

• Improve Mount Function (#18)

• • Change to CLI version of shutdown
• • Always use current kubenetes pool

• Check for valid number in backup menu (#18)

• Comments explaining some code blocks (#17)
• Spacing out code blocks for readability (#17)
• git reset for self update in case of edit (#17)
• Re-arranged functions (#17)
• after_update_actions renamed to post_process (#17)

• Exit with code 0 no matter the outcome of the script
  - This is to prevent spam in the TNS tasks manager when a user is not using prune

• Add container update checks in update_app function (#16)
• Improve rollback logic (#15)
• Use CLI version of rollback, wait for exit code to ensure valid rollback (#15)
• Skip rollback if failure during container image update (its currently impossible) (#15)